VSCode devcontainer.json mounts not working

Question

Assuming I must be doing something wrong here, but I cannot seem to get VSCode to mount anything into the container with my very simple devcontainer.json file.

It currently looks as follows:

{
    "name": "Terraform",
    "dockerFile": "Dockerfile",
    "mounts": ["source=/home/paul,target=/host,type=bind,consistency=cached"]
}

I have also tried the example given in the docs:

["source=${localEnv:HOME}${localEnv:USERPROFILE},target=/host-home-folder,type=bind,consistency=cached"]

Neither seem to mount anything inside the container, and looking at the output of the "Dev Containers" console output, it doesn't even look like VSCode attempts to mount it. Do I need to switch something on for this to work?

Running VSCode 1.36.1 on Linux Mint. Docker CE 19.03.

user_13220079 · Answer

For me it worked the workspaceMount instead of mount

"workspaceMount": "source=${localWorkspaceFolder}/sub-folder,target=/workspace,type=bind,consistency=delegated",
"workspaceFolder": "/workspace"

as stated in https://code.visualstudio.com/docs/remote/containers-advanced

user_2241064 · Answer

Looks like you'll need to VSCode 1.41+ for the mounts property to work.

Advanced containers: Add another local file mount

user_3459910 · Answer

Docker-in-Docker

Using `docker-compose`

When working with a Docker-in-Docker setup which utilizes the docker-compose functionality, the VSCode internal variable ${localWorkspaceFolder} can be used to get the actual path to the workspace on disk. This is needed because in a Docker-in-Docker environment, "normal" paths may not work as the first Docker instance is already running in a mounted environment.

In order to make those internal VSCode variables also accessible in the docker-compose.yaml, you first need to define an environment variable in your .devcontainer/devcontainer.json:

{
  "name": "DevContainer",
  "dockerFile": "Dockerfile", // this is a reference to the .devcontainer/Dockerfile, which is used by VSCode to build the DevContainer. This has nothing to do with the Dockerfile or docker-compose.yaml file your project is using.

  "remoteEnv": {
    // the original host directory which is needed for volume 
    // mount commands from inside the container (Docker in Docker)
    "HOST_PROJECT_PATH": "${localWorkspaceFolder}"
  }
}

Then, use the environment variable in your project's actual ./docker-compose.yaml:

services:
  webserver:
    image: nginx:mainline-alpine
    container_name: webserver
    ports:
      - 8080:80
    volumes:
       -  ${HOST_PROJECT_PATH}/webserver:/etc/nginx/conf.d
       -  ${HOST_PROJECT_PATH}/build:/var/www/html

VSCode provides even more internal variables which can be used for advanced setup and configuration of the DevContainer environment. Please have a look here.

Using `Dockerfile`

More information on how to use Docker-in-Docker with Dockerfiles can be found here.

user_833499 · Answer

In my case I was using a prebuilt image and avoiding the rebuild option described in notification (I tought it was referring to a full Dockerfile rebuild).

After changing the devcontainer.json with your (mount) config take care to click the rebuild button.

VSCode devcontainer.json mounts not working

4 Answers

Docker-in-Docker

Using docker-compose

Using Dockerfile

Using `docker-compose`

Using `Dockerfile`