-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Open
Labels
infrastructureBasic functionalityBasic functionality
Description
Describe the bug
Trying to start a freshly cloned project in a dev container through vscode on Windows 11 throws an error while building the devcontainer. See log details below.
Editing the devcontainer.json file and changing line 8 to "moby": false seems to work, but I have no idea if that has any bad side effects.
Steps to reproduce
- Fresh Windows 11 install with Docker desktop running on top of WSL 2
- Clone the project
- Open in dev container
...
Configuration details
Not relevantLog details
.....
> [dev_containers_target_stage 5/6] RUN --mount=type=bind,from=dev_containers_feature_content_source,source=docker-outside-of-docker_0,target=/tmp/build-features-src/docker-outside-of-docker_0 cp -ar /tmp/build-features-src/docker-outside-of-docker_0 /tmp/dev-container-features && chmod -R 0755 /tmp/dev-container-features/docker-outside-of-docker_0 && cd /tmp/dev-container-features/docker-outside-of-docker_0 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh && rm -rf /tmp/dev-container-features/docker-outside-of-docker_0:
0.231 ===========================================================================
0.231 Feature : Docker (docker-outside-of-docker)
0.231 Description : Re-use the host docker socket, adding the Docker CLI to a container. Feature invokes a script to enable using a forwarded Docker socket within a container to run Docker commands.
0.231 Id : ghcr.io/devcontainers/features/docker-outside-of-docker
0.231 Version : 1.6.5
0.231 Documentation : https://github.com/devcontainers/features/tree/main/src/docker-outside-of-docker
0.231 Options :
0.231 VERSION="latest"
0.231 MOBY="true"
0.231 MOBYBUILDXVERSION="latest"
0.231 DOCKERDASHCOMPOSEVERSION="v2"
0.231 INSTALLDOCKERBUILDX="true"
0.231 INSTALLDOCKERCOMPOSESWITCH="true"
0.231 ===========================================================================
0.245 (!) The 'moby' option is not supported on Debian 'trixie' because 'moby-cli' and related system packages have been removed from that distribution.
0.245 (!) To continue, either set the feature option '"moby": false' or use a different base image (for example: 'debian:bookworm' or 'ubuntu-24.04').
0.245 ERROR: Feature "Docker (docker-outside-of-docker)" (ghcr.io/devcontainers/features/docker-outside-of-docker) failed to install! Look at the documentation at https://github.com/devcontainers/features/tree/main/src/docker-outside-of-docker for help troubleshooting this error.
------
ERROR: failed to solve: process "/bin/sh -c cp -ar /tmp/build-features-src/docker-outside-of-docker_0 /tmp/dev-container-features && chmod -R 0755 /tmp/dev-container-features/docker-outside-of-docker_0 && cd /tmp/dev-container-features/docker-outside-of-docker_0 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh && rm -rf /tmp/dev-container-features/docker-outside-of-docker_0" did not complete successfully: exit code: 1
[10111 ms] Error: Command failed: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.80.1-1765392118165 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/go --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -f /tmp/devcontainercli-root/container-features/0.80.1-1765392118165/Dockerfile.extended -t vsc-evcc-bee0ed4408027a2bfc17fb70667e5b37a8106a9ceb842a24c188e6b1399351e6-features /tmp/devcontainercli-root/empty-folder
[10111 ms] at w6 (/root/.vscode-remote-containers/dist/dev-containers-cli-0.435.0/dist/spec-node/devContainersSpecCLI.js:467:1253)
[10111 ms] at ax (/root/.vscode-remote-containers/dist/dev-containers-cli-0.435.0/dist/spec-node/devContainersSpecCLI.js:467:997)
[10111 ms] at async Y6 (/root/.vscode-remote-containers/dist/dev-containers-cli-0.435.0/dist/spec-node/devContainersSpecCLI.js:484:3842)
[10111 ms] at async BC (/root/.vscode-remote-containers/dist/dev-containers-cli-0.435.0/dist/spec-node/devContainersSpecCLI.js:484:4957)
[10111 ms] at async p7 (/root/.vscode-remote-containers/dist/dev-containers-cli-0.435.0/dist/spec-node/devContainersSpecCLI.js:665:202)
[10111 ms] at async d7 (/root/.vscode-remote-containers/dist/dev-containers-cli-0.435.0/dist/spec-node/devContainersSpecCLI.js:664:14804)
[10111 ms] at async /root/.vscode-remote-containers/dist/dev-containers-cli-0.435.0/dist/spec-node/devContainersSpecCLI.js:484:1188
[10121 ms] Exit code 1
[10124 ms] Command failed: node /root/.vscode-remote-containers/dist/dev-containers-cli-0.435.0/dist/spec-node/devContainersSpecCLI.js up --container-session-data-folder /tmp/devcontainers-f3d47298-d9e7-4cad-a11e-cb876ef6e4f51765392111550 --workspace-folder /workspaces/evcc --workspace-mount-consistency cached --gpu-availability detect --id-label vsch.local.repository=https://github.com/TheSimpleZ/evcc.git/tree/master --id-label vsch.local.repository.volume=evcc-master-83dbd7e7f2cfe67f5ede44fb48b2e4573f32144f2c7740d10fde79f9ef4466f7 --id-label vsch.local.repository.folder=evcc --id-label devcontainer.config_file=/workspaces/evcc/.devcontainer/devcontainer.json --log-level debug --log-format json --config /workspaces/evcc/.devcontainer/devcontainer.json --override-config /tmp/devcontainer-3b916a2c-551d-46c5-b536-6d824b41d648.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=evcc-master-83dbd7e7f2cfe67f5ede44fb48b2e4573f32144f2c7740d10fde79f9ef4466f7,target=/workspaces,external=true --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default off --mount-workspace-git-root --include-configuration --include-merged-configuration
.....
What type of operating system or environment does evcc run on?
Windows
External automation
- I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.
Nightly build
- I have verified that the issue is reproducible with the latest nightly build
Version
Latest master
Metadata
Metadata
Assignees
Labels
infrastructureBasic functionalityBasic functionality