Codespace not working #4540

jaulz · 2021-07-07T20:54:28Z

jaulz
Jul 7, 2021

Unfortunately, my codespace at https://jaulz-collect-expert-wrr5j76w296r7.github.dev/ is once again stuck and I cannot start it. It keeps on saying "starting the codespace". Could someone from GitHub please send me the files or push the commits which were not yet pushed? For some reason I can neither export these changes to another branch. Thanks a lot in advance!

Answered by tanmayeekamath

Jul 27, 2021

@jaulz, @driesvints Apologies for the delay. Are you still experiencing this issue?

View full answer

jaulz · 2021-07-08T07:15:43Z

jaulz
Jul 8, 2021
Author

I could recover all my changes via the vscode integration! Thanks for that magical piece! 😊
Though, still it says that it cannot start the container and this is the log:

Configuration starting...
2021-07-08T07:12:10: [2021-07-08T07:12:11.294Z] @microsoft/vscode-dev-containers-cli 0.41.0.
[2021-07-08T07:12:11.294Z] Start: Resolving Remote
[2021-07-08T07:12:11.385Z] Start: Run: docker ps -q -a --filter label=Type=codespaces
[2021-07-08T07:12:11.426Z] Stop (41 ms): Run: docker ps -q -a --filter label=Type=codespaces
[2021-07-08T07:12:11.427Z] Start: Run: docker inspect --type container 74056aa9d4bc
[2021-07-08T07:12:11.469Z] Stop (42 ms): Run: docker inspect --type container 74056aa9d4bc
[2021-07-08T07:12:11.469Z] Start: Starting container
[2021-07-08T07:12:11.470Z] Start: Run: docker start 74056aa9d4bc6b76b72ae0c72dd2b0ee69928743fe9aaa1ee016ced8f75eaba3
[2021-07-08T07:12:12.903Z] Stop (1433 ms): Run: docker start 74056aa9d4bc6b76b72ae0c72dd2b0ee69928743fe9aaa1ee016ced8f75eaba3
[2021-07-08T07:12:12.904Z] Stop (1435 ms): Starting container
[2021-07-08T07:12:12.904Z] Start: Run: docker ps -q -a --filter label=Type=codespaces
[2021-07-08T07:12:12.946Z] Stop (42 ms): Run: docker ps -q -a --filter label=Type=codespaces
[2021-07-08T07:12:12.946Z] Start: Run: docker inspect --type container 74056aa9d4bc
[2021-07-08T07:12:12.998Z] Stop (52 ms): Run: docker inspect --type container 74056aa9d4bc
[2021-07-08T07:12:12.999Z] Start: Inspecting container
[2021-07-08T07:12:12.999Z] Start: Run: docker inspect --type container 74056aa9d4bc6b76b72ae0c72dd2b0ee69928743fe9aaa1ee016ced8f75eaba3
[2021-07-08T07:12:13.050Z] Stop (51 ms): Run: docker inspect --type container 74056aa9d4bc6b76b72ae0c72dd2b0ee69928743fe9aaa1ee016ced8f75eaba3
[2021-07-08T07:12:13.050Z] Stop (51 ms): Inspecting container
[2021-07-08T07:12:13.051Z] Start: Run in container: /bin/sh
[2021-07-08T07:12:13.055Z] Start: Run in container: uname -m
[2021-07-08T07:12:13.182Z] x86_64
[2021-07-08T07:12:13.182Z] 
[2021-07-08T07:12:13.182Z] Stop (127 ms): Run in container: uname -m
[2021-07-08T07:12:13.182Z] Start: Run in container: (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null
[2021-07-08T07:12:13.188Z] NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.13.5
PRETTY_NAME="Alpine Linux v3.13"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/"
[2021-07-08T07:12:13.188Z] 
[2021-07-08T07:12:13.188Z] Stop (6 ms): Run in container: (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null
[2021-07-08T07:12:13.188Z] Start: Run in container: cat /etc/passwd
[2021-07-08T07:12:13.189Z] Stop (1 ms): Run in container: cat /etc/passwd
[2021-07-08T07:12:13.190Z] Start: Run in container: test -d /root/.vscode-remote
[2021-07-08T07:12:13.211Z] 
[2021-07-08T07:12:13.211Z] 
[2021-07-08T07:12:13.211Z] Stop (21 ms): Run in container: test -d /root/.vscode-remote
[2021-07-08T07:12:13.212Z] Start: Run in container: test -f /var/vscode-remote/.patchEtcEnvironmentMarker
[2021-07-08T07:12:13.218Z] 
[2021-07-08T07:12:13.218Z] 
[2021-07-08T07:12:13.218Z] Stop (6 ms): Run in container: test -f /var/vscode-remote/.patchEtcEnvironmentMarker
[2021-07-08T07:12:13.218Z] Start: Run in container: test -f /var/vscode-remote/.patchEtcProfileMarker
[2021-07-08T07:12:13.219Z] 
[2021-07-08T07:12:13.219Z] 
[2021-07-08T07:12:13.219Z] Stop (1 ms): Run in container: test -f /var/vscode-remote/.patchEtcProfileMarker
[2021-07-08T07:12:13.219Z] Start: Run in container: test ! -f '/root/.vscode-remote/data/Machine/.writeMachineSettingsMarker' && set -o noclobber && mkdir -p '/root/.vscode-remote/data/Machine' && { > '/root/.vscode-remote/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null
[2021-07-08T07:12:13.225Z] 
[2021-07-08T07:12:13.225Z] 
[2021-07-08T07:12:13.225Z] Exit code 1
[2021-07-08T07:12:13.225Z] Stop (6 ms): Run in container: test ! -f '/root/.vscode-remote/data/Machine/.writeMachineSettingsMarker' && set -o noclobber && mkdir -p '/root/.vscode-remote/data/Machine' && { > '/root/.vscode-remote/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null
[2021-07-08T07:12:13.225Z] Start: Run in container: cat /root/.vscode-remote/data/Machine/settings.json
[2021-07-08T07:12:13.227Z] 
[2021-07-08T07:12:13.227Z] cat: /root/.vscode-remote/data/Machine/settings.json: No such file or directory
[2021-07-08T07:12:13.227Z] Exit code 1
[2021-07-08T07:12:13.227Z] Stop (2 ms): Run in container: cat /root/.vscode-remote/data/Machine/settings.json
[2021-07-08T07:12:13.227Z] Stop (1933 ms): Resolving Remote
[2021-07-08T07:12:13.656Z] @microsoft/vscode-dev-containers-cli 0.41.0.
[2021-07-08T07:12:13.656Z] Start: Resolving Remote
[2021-07-08T07:12:13.669Z] Start: Run: docker ps -q -a --filter label=Type=codespaces
[2021-07-08T07:12:13.710Z] Stop (41 ms): Run: docker ps -q -a --filter label=Type=codespaces
[2021-07-08T07:12:13.711Z] Start: Run: docker inspect --type container 74056aa9d4bc
[2021-07-08T07:12:13.753Z] Stop (42 ms): Run: docker inspect --type container 74056aa9d4bc
[2021-07-08T07:12:13.754Z] Start: Inspecting container
[2021-07-08T07:12:13.754Z] Start: Run: docker inspect --type container 74056aa9d4bc6b76b72ae0c72dd2b0ee69928743fe9aaa1ee016ced8f75eaba3
[2021-07-08T07:12:13.795Z] Stop (41 ms): Run: docker inspect --type container 74056aa9d4bc6b76b72ae0c72dd2b0ee69928743fe9aaa1ee016ced8f75eaba3
[2021-07-08T07:12:13.796Z] Stop (42 ms): Inspecting container
[2021-07-08T07:12:13.796Z] Start: Run in container: /bin/sh
[2021-07-08T07:12:13.800Z] Start: Run in container: uname -m
[2021-07-08T07:12:13.923Z] x86_64
[2021-07-08T07:12:13.923Z] 
[2021-07-08T07:12:13.923Z] Stop (123 ms): Run in container: uname -m
[2021-07-08T07:12:13.923Z] Start: Run in container: (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null
[2021-07-08T07:12:13.925Z] NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.13.5
PRETTY_NAME="Alpine Linux v3.13"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/"
[2021-07-08T07:12:13.925Z] 
[2021-07-08T07:12:13.925Z] Stop (2 ms): Run in container: (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null
[2021-07-08T07:12:13.925Z] Start: Run in container: cat /etc/passwd
[2021-07-08T07:12:13.927Z] Stop (2 ms): Run in container: cat /etc/passwd
[2021-07-08T07:12:13.928Z] Start: Run in container: test -d /root/.vscode-remote
[2021-07-08T07:12:13.929Z] 
[2021-07-08T07:12:13.929Z] 
[2021-07-08T07:12:13.929Z] Stop (1 ms): Run in container: test -d /root/.vscode-remote
[2021-07-08T07:12:13.929Z] Start: Run in container: test -f /var/vscode-remote/.patchEtcEnvironmentMarker
[2021-07-08T07:12:13.930Z] 
[2021-07-08T07:12:13.930Z] 
[2021-07-08T07:12:13.930Z] Stop (1 ms): Run in container: test -f /var/vscode-remote/.patchEtcEnvironmentMarker
[2021-07-08T07:12:13.930Z] Start: Run in container: test -f /var/vscode-remote/.patchEtcProfileMarker
[2021-07-08T07:12:13.931Z] 
[2021-07-08T07:12:13.931Z] 
[2021-07-08T07:12:13.931Z] Stop (1 ms): Run in container: test -f /var/vscode-remote/.patchEtcProfileMarker
[2021-07-08T07:12:13.931Z] Start: Run in container: test ! -f '/root/.vscode-remote/data/Machine/.writeMachineSettingsMarker' && set -o noclobber && mkdir -p '/root/.vscode-remote/data/Machine' && { > '/root/.vscode-remote/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null
[2021-07-08T07:12:13.932Z] 
[2021-07-08T07:12:13.932Z] 
[2021-07-08T07:12:13.932Z] Exit code 1
[2021-07-08T07:12:13.932Z] Stop (1 ms): Run in container: test ! -f '/root/.vscode-remote/data/Machine/.writeMachineSettingsMarker' && set -o noclobber && mkdir -p '/root/.vscode-remote/data/Machine' && { > '/root/.vscode-remote/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null
[2021-07-08T07:12:13.932Z] Start: Run in container: cat /root/.vscode-remote/data/Machine/settings.json
[2021-07-08T07:12:13.933Z] 
[2021-07-08T07:12:13.933Z] cat: /root/.vscode-remote/data/Machine/settings.json: No such file or directory
[2021-07-08T07:12:13.933Z] Exit code 1
[2021-07-08T07:12:13.933Z] Stop (1 ms): Run in container: cat /root/.vscode-remote/data/Machine/settings.json
[2021-07-08T07:12:13.933Z] userEnvProbe: none (default)
[2021-07-08T07:12:13.934Z] Start: Run in container: test ! -f '/root/.vscode-remote/data/Machine/.onCreateCommandMarker' && set -o noclobber && mkdir -p '/root/.vscode-remote/data/Machine' && { > '/root/.vscode-remote/data/Machine/.onCreateCommandMarker' ; } 2> /dev/null
[2021-07-08T07:12:13.935Z] 
[2021-07-08T07:12:13.935Z] 
[2021-07-08T07:12:13.935Z] Stop (1 ms): Run in container: test ! -f '/root/.vscode-remote/data/Machine/.onCreateCommandMarker' && set -o noclobber && mkdir -p '/root/.vscode-remote/data/Machine' && { > '/root/.vscode-remote/data/Machine/.onCreateCommandMarker' ; } 2> /dev/null
[2021-07-08T07:12:13.935Z] Start: Run in container: test ! -f '/root/.vscode-remote/data/Machine/.updateContentCommandMarker' && set -o noclobber && mkdir -p '/root/.vscode-remote/data/Machine' && { > '/root/.vscode-remote/data/Machine/.updateContentCommandMarker' ; } 2> /dev/null
[2021-07-08T07:12:13.937Z] 
[2021-07-08T07:12:13.937Z] 
[2021-07-08T07:12:13.937Z] Stop (2 ms): Run in container: test ! -f '/root/.vscode-remote/data/Machine/.updateContentCommandMarker' && set -o noclobber && mkdir -p '/root/.vscode-remote/data/Machine' && { > '/root/.vscode-remote/data/Machine/.updateContentCommandMarker' ; } 2> /dev/null
[2021-07-08T07:12:13.937Z] Start: Run in container: test ! -f '/root/.vscode-remote/data/Machine/.postCreateCommandMarker' && set -o noclobber && mkdir -p '/root/.vscode-remote/data/Machine' && { > '/root/.vscode-remote/data/Machine/.postCreateCommandMarker' ; } 2> /dev/null
[2021-07-08T07:12:13.937Z] Stop (281 ms): Resolving Remote
[2021-07-08T07:12:13.939Z] 
[2021-07-08T07:12:13.939Z] 
[2021-07-08T07:12:13.939Z] Stop (2 ms): Run in container: test ! -f '/root/.vscode-remote/data/Machine/.postCreateCommandMarker' && set -o noclobber && mkdir -p '/root/.vscode-remote/data/Machine' && { > '/root/.vscode-remote/data/Machine/.postCreateCommandMarker' ; } 2> /dev/null
[2021-07-08T07:12:13.939Z] Start: Run in container: mkdir -p '/root/.vscode-remote/data/Machine' && [ "$(cat '/root/.vscode-remote/data/Machine/.postStartCommandMarker' 2>/dev/null)" != '2021-07-08T07:12:12.813611954Z' ] && echo '2021-07-08T07:12:12.813611954Z' > '/root/.vscode-remote/data/Machine/.postStartCommandMarker'
[2021-07-08T07:12:13.941Z] 
[2021-07-08T07:12:13.941Z] 
[2021-07-08T07:12:13.941Z] Stop (2 ms): Run in container: mkdir -p '/root/.vscode-remote/data/Machine' && [ "$(cat '/root/.vscode-remote/data/Machine/.postStartCommandMarker' 2>/dev/null)" != '2021-07-08T07:12:12.813611954Z' ] && echo '2021-07-08T07:12:12.813611954Z' > '/root/.vscode-remote/data/Machine/.postStartCommandMarker'
```

0 replies

driesvints · 2021-07-13T09:08:07Z

driesvints
Jul 13, 2021

I also seem to be experiencing the same thing. Not sure if it's meant to share my codespace url publicly here.

0 replies

tanmayeekamath · 2021-07-27T23:00:21Z

tanmayeekamath
Jul 27, 2021

@jaulz, @driesvints Apologies for the delay. Are you still experiencing this issue?

11 replies

driesvints Jul 31, 2021

Thanks @jkeech.

Could the share the url for one of your codespaces that is not connecting?

https://driesvints-laravelio-laravel-io-q7xjg4x3966w.github.dev

Do codespaces on other repositories open for you?

Yes, I'm able to create them on other repos. Please note that the current workspace that's not working was in fact working at first but suddenly stopped at some point.

Do you have any firewall or proxy that could be interfering with the connection?

No

Do any errors show up in the console or network tab when connecting?

No errors, just a whole bunch of these:

jkeech Aug 1, 2021

@driesvints, thanks for sending the link to your codespace. I see what is happening now. The codespace is in the middle of a rebuild which started on July 13. The codespace was originally created and then went through a couple rebuilds within 30 minutes of creation, but the last rebuild never finished. Rebuild operations currently do not have a timeout, which is a bug. If there's something in the devcontainer scripts that causes the rebuild to never complete, it will hang in the rebuilding state. We will work on a fix to add a timeout for rebuilds so that they will automatically stop if they don't complete within a certain time.

To get back into this codespace, the best action would be to stop it, which you can do from VS Code via the Codespaces: Stop Codespace command (or via the right-click option on the codespace in the remote explorer). Once it stops, you should be able to restart it. Since it was stopped in the middle of a rebuild, when you next start the codespace, it should end up in the recovery container where you can edit the devcontainer config and then retry the rebuild. Let us know if you have any problems during these steps. Thanks!

driesvints Aug 2, 2021

Hey @jkeech, thanks. After stopping and restarting the codespace I can indeed visit it once again but now I'm getting:

With:

Configuration starting...
2021-08-02T08:42:28: [2021-08-02T08:42:28.681Z] @microsoft/vscode-dev-containers-cli 0.42.0.
[2021-08-02T08:42:28.681Z] Start: Resolving Remote
[2021-08-02T08:42:28.751Z] Start: Run: docker ps -q -a --filter label=Type=codespaces
Error: The expected container does not exist.
    at vp (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/node/devContainersCLI.js:279:8003)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async lL (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/node/devContainersCLI.js:279:3898)
    at async i8 (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/node/devContainersCLI.js:247:9700)
    at async $G (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/node/devContainersCLI.js:293:7173)
    at async Kae (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/node/devContainersCLI.js:293:26145)
    at async Yae (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/node/devContainersCLI.js:293:25739)
[2021-08-02T08:42:28.805Z] Stop (54 ms): Run: docker ps -q -a --filter label=Type=codespaces
Failed to create container.Error: The expected container does not exist.Error Code: 1302Container creation failed.
2021-08-02T08:42:29: Creating recovery container.
2021-08-02T08:42:29:

jkeech Aug 2, 2021

@driesvints, glad that worked!

The recovery container is expected since the codespace was stopped in the middle of the rebuild and the rebuild did not end up with a working container. The same thing would happen if you have a typo in the Dockerfile or if other devcontainer scripts fail and end up without a working container image. You can continue modifying your devcontainer config from inside the recovery container and then running the Rebuild command again to iterate on the image configuration for your codespace. You should also be able to commit and push out any code you'd like when in the recovery container.

driesvints Aug 3, 2021

Thanks @jkeech. I ended up destroying the codespace and creating a new one. Now it's all working properly again.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Community

Codespace not working #4540

{{title}}

Replies: 3 comments 11 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

Codespace not working #4540

Replies: 3 comments · 11 replies

jaulz Jul 8, 2021 Author

Replies: 3 comments 11 replies

jaulz
Jul 8, 2021
Author