microsoft / microsoft/vscode-remote-release
If /tmp/devcontainercli-$USER does not exist, devcontainer fails to start
@chrmarti is already working on this.
Since Oct 30, 2023.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
We have a new issue where one of our devcontainers do not start the first time after reboot.
It must be rebuilt before it works.
This devcontainer uses docker-compose and building from the compose-file.
I can reproduce it 100% of the time with this devcontainer but not with our other devcontainers.
I have created a repo which reproduces this issue: https://github.com/staffanf/vscode-remote-release-issue-9138
-
VSCode Version: 1.83.1
-
Local OS Version: Ubuntu 22.04.3 LTS
-
Remote OS Version: Ubuntu 22.04.3 LTS docker container
-
Remote Extension/Connection Type: Containers
-
Logs:
remoteContainers-2023-10-26T11-54-28.837Z.log
Steps to Reproduce:
- Reboot machine or manually remove /tmp/devcontainercli-$USER/
- Open a devcontainer using docker-compose
- ERROR: Starting devcontainer crashes with error since it's missing this tmp file
- Reopen locally
- Rebuild and reopen container
- Container starts normally
Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No
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.