Devcontainer features don't work behind proxy if docker-compose.yml is used

[maederm]

Hi

I have an issue using a devcontainers on Mac OS behind a tls-intercepting corporate proxy in vscode. Basically I can build the container using image and features. But when I use dockerComposeFile and features it gives me an error:

ERROR: Feature "Poetry (via pipx)" (ghcr.io/devcontainers-contrib/features/poetry) failed to install
failed to solve: process "/bin/sh -c cp -ar /tmp/build-features-src/poetry_0 /tmp/dev-container-features  && chmod -R 0755 /tmp/dev-container-features/poetry_0  && cd /tmp/dev-container-features/poetry_0  && chmod +x ./devcontainer-features-install.sh  && ./devcontainer-features-install.sh  && rm -rf /tmp/dev-container-features/poetry_0" did not complete successfully: exit code: 7

I'm not really sure in which repo I should open the issue.

Docker Compose that doesn't work

devcontainer.json

{
	"name": "Python 3 docker-compose",
	"dockerComposeFile":[
		"docker-compose.yml"
	],
	"service": "devcontainer",
	"workspaceFolder": "/workspace",
	"features": {
		"ghcr.io/devcontainers-contrib/features/poetry:2": {}
	}
}

docker-compose.yml

version: '3.7'
services:
  devcontainer:
    image: mcr.microsoft.com/devcontainers/python:1-3.12-bullseye
    volumes:
      - ..:/workspace:cached
    command: sleep infinity

Plain Image that works

devcontainer.json

{
	"name": "Python 3 direct",
	"image": "mcr.microsoft.com/devcontainers/python:1-3.12-bullseye",
	"features": {
		"ghcr.io/devcontainers-contrib/features/poetry:2": {}
	}
}

Do I miss something in the docker compose variant?

You can find the full logs and environment details here: https://github.com/maederm/devcontainer-proxy-issue

[samruddhikhandale]

Hi 👋

Are you facing issues where downloading the Feature fails? If yes, then devcontainers/cli#281 looks related.

However, if that's not the case, then I wonder if devcontainers-contrib/features/poetry needs to be updated to support proxy similar to first party dev container Features (eg. Python)

[maederm]

Hi @samruddhikhandale

Are you facing issues where downloading the Feature fails? If yes, then devcontainers/cli#281 looks related.

I don't see the errors in devcontainers/cli#281.

However, if that's not the case, then I wonder if devcontainers-contrib/features/poetry needs to be updated to support proxy similar to first party dev container Features (eg. Python)

I belive the feature supports proxy etc. because it works if I don't use docker-compose.yml but directly specify the image and feature in devcontainer.json.

Could it be that different env-variables get injected during build time when using docker-compose.yml instead of using devcontainer.json directly?

Should I open an issue with vscode or devcontainer-cli?