| DTP1001 |
Host port not found |
In the Docker Compose project, the Service URL specifies the token {ServicePort}, but the container doesn't have any corresponding host port. |
Ensure the container is started with a host port for the right URL scheme (http or https). |
| DTP1002 |
Container not found |
When debugging the Docker Compose project, the container wasn't started or container exited. |
See the Output window for more detail on why the container failed to start. |
| DTP1003 |
No service found while debugging the Docker Compose project. |
|
Ensure that the Docker Compose document has one or more dotnet services defined. |
| DTP1004 |
Docker Compose scaffolding error |
|
Try adding Docker Compose support again. |
| DT1001 |
Debugging failed due to an error running Docker Compose command. |
See the Output window for more detail on this error. |
|
| DT1002 |
Invalid target OS |
Unknown Dockerfile target OS specified in DockerDefaultTargetOS property. |
Supported values are 'Windows' and 'Linux'. |
| DT1003 |
An unexpected error while trying to execute a command. |
|
See the Output window for more detail on this error. |
| DT1004 |
Error in Docker Compose file |
|
Check all Docker Compose documents and make sure they are valid. |
| DT1005 |
Docker Compose command execution failure |
|
See the Output window for more detail on this error. |
| DT1006 |
The Compose profile name used in the active launch profile isn't found in the Docker Compose document. |
For example, if the active launch profile is using Compose profile called p2 as shown here:
"Docker Compose": {
"commandName": "DockerCompose",
"commandVersion": "1.0",
"composeProfile": {
"includes": [
"p2"
]
}
}
but docker-compose.yml didn't define the profile p2, then you see this error. |
Update the launch profile to use the right Compose profile or use the Manage Docker Compose Launch Settings dialog to update the launch settings. |
| DT1007 |
Invalid service name in the active launch profile that uses Compose profile. |
For example, if the active launch profile is using Compose profile p1 and defines the service list for the Compose profile p1 as shown here:
"Docker Compose": {
"commandName": "DockerCompose",
"commandVersion": "1.0",
"composeProfile": {
"includes": [
"p1"
],
"serviceActions": {
"webapp2": "StartWithoutDebugging"
}
}
}
but docker-compose.yml doesn't define the service webapp2, then you see this error. |
Update the launch profile to use the right service name or use the Manage Docker Compose Launch Settings dialog to update the launch settings. |
| DT1008 |
Invalid service action in the active launch profile that uses Compose profile. |
For example, if the active launch profile is using Compose profile p1 and defines the wrong action (wrongActionname) for a service (webapplication).
"Docker Compose": { "commandName": "DockerCompose",
"commandVersion": "1.0",
"composeProfile": {
"includes": [
"p1"
],
"serviceActions": {
"webapp": "wrongActionname"
}
}
}
|
Correct the service action to StartWithoutDebugging, which is the only valid action for service that uses a Compose profile. |
| DT1009 |
Active launch profile is using both composeProfile and serviceActions. |
A Visual Studio launch profile can be defined either using Compose profiles or picking and choosing a service list without using a Compose profile; it can't be created using both. So if an active launch profile uses both as shown below, then you see this error.
"Docker Compose": {
"commandName": "DockerCompose",
"commandVersion": "1.0",
"composeProfile": {
"includes": [
"p1"
]
},
"serviceActions": {
"webapp": "StartWithoutDebugging"
}
} |
Use either composeProfile or serviceActions or use the Manage Docker Compose Launch Settings dialog to update the launch settings. |
| DT1010 |
Invalid service name in the active launch profile |
For example, if the active launch profile defines the serviceActions as shown here:
"Docker Compose": {
"commandName": "DockerCompose",
"commandVersion": "1.0",
"serviceActions": {
"redis1": "StartWithoutDebugging",
"webapp8": "StartWithoutDebugging"
}
}
But the docker-compose.yml didn't define the service redis1, then you see this error. |
Update the launch profile to use the right service name or use the Manage Docker Compose Launch Settings dialog to update the launch settings. |
| DT1011 |
Invalid service action in the active launch profile. |
For example, if the active launch profile uses the wrong service action (wrongAction) as shown below, then you see this error.
"Docker Compose": {
"commandName": "DockerCompose",
"commandVersion": "1.0",
"serviceActions": {
"webapplication8": "wrongAction"
}
}
|
Correct the service action to one of DoNotStart, StartDebugging, or StartWithoutDebugging. Or use Manage Docker Compose Launch Settings dialog to update the launch settings. |
| DT1012 |
Invalid launch profile. Both composeProfile and serviceActions are missing. |
A Visual Studio launch profile can be defined either using Compose profiles or by picking and choosing a service list without using a Compose profile. But the active launch profile is defined with none of them. |
Use the Manage Docker Compose Launch Settings dialog to update the launch settings. |
| DT1013 |
The active launch profile isn't found |
|
Ensure the active launch profile is defined in launchSettings.json. |
| DT1014 |
Invalid profile version. |
For example, if the active launch profile defines an unknown command version (10.0):
"Docker Compose":
"commandName": "DockerCompose",
"commandVersion": "10.0",
"serviceActions": {
"webapp8": "StartDebugging",
"redis": "StartWithoutDebugging"
}
}
|
Please see the error message for the supported commandVersion, or use the Manage Docker Compose Launch Settings dialog to update the launch settings. |
| DT1015 |
Unsupported old profile version. |
|
The profile version is no longer supported by the current Visual Studio. Please upgrade the profile to the latest supported version using the Manage Docker Compose Launch Settings dialog to update the launch settings. |
| DT1016 |
Using profile from newer version of Visual Studio |
|
The profile version is higher than the current supported version. Please upgrade the Visual Studio to the latest version. |
| DT1017 |
Using profile from newer version of Visual Studio, but continues to work |
This is a warning message |
The profile version is higher than the current supported version, but still compatible with the current version of Visual Studio, but might be missing some features. |
| DT1018 |
Using old profile version, but compatible. |
This is a warning message |
The profile version is lower than the latest version, but still compatible. Some of the newer features might not work. Consider upgrading to the latest version of Visual Studio. |
| DT1019 |
Unsupported compose v2 |
You're using older version of Docker Compose v2 that doesn't support the Compose profile. |
Upgrade Docker Compose to the latest version. |