VSCode Remote Container - extensions not installing on dev container using docker-compose

Question

I am having trouble getting extensions installed in the dev container using "Remote - Containers". I do not know if it's a bug, incorrect configuration on my end, or intended behaviour. Down below is my current configuration, both files are located in the root folder of the project.

docker-compose.yml

version: "3.7"

services:
  api:
    image: node:12
    restart: always
    ports:
      - ${API_PORT}:3000
    volumes:
      - .:/usr/app
      - /usr/app/node_modules
    working_dir: /usr/app
    command: bash -c "yarn && yarn dev"

.devcontainer.json

{
    "dockerComposeFile": "docker-compose.yml",
    "service": "api",
    "workspaceFolder": "/usr/app",
    "extensions": [
        "eamodio.gitlens",
        "formulahendry.auto-rename-tag",
        "coenraads.bracket-pair-colorizer-2",
        "kumar-harsh.graphql-for-vscode",
        "esbenp.prettier-vscode",
        "ms-vscode.vscode-typescript-tslint-plugin",
        "visualstudioexptteam.vscodeintellicode"
    ]
}

The list of extensions listed in the .devontainer.json are the ones I want to have installed in the dev container. Any help is appreciated!

It worked when I set it up on a different computer. It probably was an issue with caching or similar. — rosengrenen
– rosengrenen, Commented May 5, 2019 at 17:24

Jeremy Caney · Accepted Answer · 2020-05-08 01:22:06Z

13

According to the Visual Studio Code documentation, the two files need to be located in a directory .devcontainer in the workspace root.

I still had issues installing the extensions while working from behind a corporate proxy. The solution was to give the container access to the proxy server:

If you use an authenticating proxy like Cntlm on your local machine, configure it to listen on 172.17.0.1 (the Docker interface). Then define the http_proxy and https_proxy environment variables for the container. For example, in devcontainer.json:

"containerEnv": { 
  "http_proxy": "http://172.17.0.1:3128",
  "https_proxy": "http://172.17.0.1:3128"
}

Or in docker-compose.yaml

services:
  devcontainer:
    environment:
      http_proxy: http://172.17.0.1:3128
      https_proxy: http://172.17.0.1:3128

Or configure docker-compose.yaml to make the container use the host network:

services:
  devcontainer:
    network_mode: host

Then you can just pass the same proxy variables into the container as used on the host. For example, in the docker-compose.yaml:

services:
  devcontainer:
    environment:
      http_proxy: $http_proxy
      https_proxy: $https_proxy

If you are not using a local, but rather a remote proxy inside of your network, you can do the latter regardless of the container's network configuration (host or default).

edited May 8, 2020 at 1:22

Jeremy Caney

7,808115 gold badges58 silver badges86 bronze badges

answered May 7, 2020 at 15:36

clssn

1311 silver badge4 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Jeremy Caney Over a year ago

This is a really nice first post. Thank you for putting so much detail into it.

esg Over a year ago

Was going around in circles and needed to be spoonfed that 172.17.0.1 was a Docker-relevant interface to believe this approach was worth trying. Thanks for the guidance!

Nejc Galof · Accepted Answer · 2022-09-12 15:51:21Z

2

I also have issues installing the extensions while working from behind a corporate proxy. The solution was to give the container access to the proxy server and set HTTP proxy strict SSL:

"settings": {
    "http.proxy": "(your_proxy_host:port)",
    "http.proxyStrictSSL": false
},

answered Sep 12, 2022 at 15:51

Nejc Galof

2,6343 gold badges36 silver badges72 bronze badges

1 Comment

TsK Feb 4 at 21:44

Three years later, same issue

Brent Bradburn · Accepted Answer · 2022-04-14 00:16:03Z

This answer is only applicable if your network environment requires the use of a proxy server.

According to "Known limitations" of "Developing inside a Container"...

Local proxy settings are not reused inside the container, which can prevent extensions from working unless the appropriate proxy information is configured (for example global HTTP_PROXY or HTTPS_PROXY environment variables with the appropriate proxy information).

I was able to set the proxy environment variables by appending to runArgs in 'devcontainer.json': "--net=host", "--env=https_proxy=(your_proxy_host:port)".

Alternatively, if host-access is not required for the proxy, you can just append to '.devcontainer/Dockerfile':

ENV https_proxy=(your_proxy_host:port)

Enabling proxy access in this way may also be necessary for network access from your application (not just for vscode extensions).

See also: How do I pass environment variables to Docker containers?

Collectives™ on Stack Overflow

VSCode Remote Container - extensions not installing on dev container using docker-compose

3 Answers 3

2 Comments

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related