microsoft / microsoft/vscode-remote-release
Dev Containers silently fails when docker-compose is missing
@chrmarti is already working on this.
Since Jan 13, 2023.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
-
VSCode Version: 1.74.3
-
Local OS Version: Ubuntu 20.04
-
Remote OS Version: n/a
-
Remote Extension/Connection Type: Containers
-
Logs:
2023-01-11 14:17:16.266 [error] {"message":"Command failed: /usr/share/code/code --ms-enable-electron-run-as-node /home/user/.vscode/extensions/ms-vscode-remote.remote-containers-0.266.1/dist/spec-node/devContainersSpecCLI.js read-configuration --workspace-folder /path/to/repo --log-level debug --log-format json --config /path/to/repo/.devcontainer/devcontainer.json --include-merged-configuration --mount-workspace-git-root true","code":1} remote-containers.reopenInContainer {"value":"ms-vscode-remote.remote-containers","c":"ms-vscode-remote.remote-containers"}
Steps to Reproduce:
- Remove docker-compose (or just don't install it in the first place)
- Install Dev Containers extension
- Open a folder with a .devcontainer folder
- Select "Reopen in Container"
The .devcontainer/devcontainer.json file has "dockerComposeFile": ["docker-compose-debug.yml"],
I get no visible errors, no CPU load, nothing to let me know if anything is happening (or not happening).
However... if the docker image exists, then I do get a visible error telling me that docker-compose is required. I found this out when trying to reproduce for this bug report... but it seems unlikely a user will not have docker-compose, but have the docker container to be built by docker-compose...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.