



Whether to remove the debug container after debugging. Similar to serverReadyAction, but replaces container ports with host ports. Options for launching a browser to the Docker container. Name of the container used for debugging. More information about debugging Node.js applications within Docker containers can be found at Debug Node.js within a container.Įxample launch.json configuration for debugging a Node.js application: Configuration reference Property If you already have a functional Dockerfile, we recommend using the Docker: Initialize for Docker debugging command to scaffold a launch configuration and Docker-related tasks. command to create these items, if none of these assets already exist. We recommend using the Docker: Add Docker Files to Workspace. A launch configuration that invokes these tasks.docker-build and docker-run tasks in tasks.json.To successfully run a Docker launch configuration, you must have: Scaffolding or pasting a launch configuration into launch.json is not sufficient to build and debug a Docker container. NET applications within Docker containers. The Docker extension currently supports debugging Node.js, Python, and. This provider is configured via entries within launch.json, with configuration being specific to each application platform supported by the provider. The Docker extension provides a docker debug configuration provider that manages how VS Code will launch an application and/or attach a debugger to the application in a running Docker container. The Docker extension provides more support for debugging applications within Docker containers, such as scaffolding launch.json configurations for attaching a debugger to applications running within a container. Configure IntelliSense for cross-compiling.
