Error reconnecting to existing Codespace

[danfarinoeyecue]

For the past couple of days, we've been getting this error when reconnecting to an existing Codespace. Since it was last working, there have been no changes to our docker-compose.yml or other devcontainer config files.

ERROR: build path /tmp/__devcontainers_cli_empty__ either does not exist, is not accessible, or is not a valid URL. seems to be the meat of the issue.

Rebuilding the container after this error works and will get us back to a working codespace (however, this is inconvenient to have to wait for the rebuild and then start from a fresh environment).

Thanks!

2022-06-30 16:24:18.706Z: $ docker -v
2022-06-30 16:24:18.721Z: Stop (35 ms): Run: docker -v
2022-06-30 16:24:18.736Z: $ docker events --format {{json .}} --filter event=start
2022-06-30 16:24:18.753Z: PersistedPath=/var/lib/docker/codespacemount/.persistedshare, ContainerHasLabels=true
2022-06-30 16:24:18.768Z: Container was created with these config files: /var/lib/docker/codespacemount/workspace/foo-dev/.devcontainer/docker-compose.yml,/var/lib/docker/codespacemount/.persistedshare/docker-compose.codespaces.yml,/var/lib/docker/codespacemount/.persistedshare/docker-compose/docker-compose.devcontainer.build-1656605616368.yml,/var/lib/docker/codespacemount/.persistedshare/docker-compose/docker-compose.devcontainer.containerFeatures-1656605684649.yml
2022-06-30 16:24:18.784Z: Restoring /var/lib/docker/codespacemount/.persistedshare/docker-compose/docker-compose.devcontainer.build-1656605616368.yml from persisted storage
2022-06-30 16:24:18.813Z: Restoring /var/lib/docker/codespacemount/.persistedshare/docker-compose/docker-compose.devcontainer.containerFeatures-1656605684649.yml from persisted storage
2022-06-30 16:24:18.828Z: $ docker-compose --project-name foo-dev_devcontainer -f /var/lib/docker/codespacemount/workspace/foo-dev/.devcontainer/docker-compose.yml -f /var/lib/docker/codespacemount/.persistedshare/docker-compose.codespaces.yml -f /var/lib/docker/codespacemount/.persistedshare/docker-compose/docker-compose.devcontainer.build-1656605616368.yml -f /var/lib/docker/codespacemount/.persistedshare/docker-compose/docker-compose.devcontainer.containerFeatures-1656605684649.yml up -d --no-recreate
2022-06-30 16:24:18.842Z: ERROR: build path /tmp/__devcontainers_cli_empty__ either does not exist, is not accessible, or is not a valid URL.
2022-06-30 16:24:18.858Z: Stop (574 ms): Run: docker-compose --project-name foo-dev_devcontainer -f /var/lib/docker/codespacemount/workspace/foo-dev/.devcontainer/docker-compose.yml -f /var/lib/docker/codespacemount/.persistedshare/docker-compose.codespaces.yml -f /var/lib/docker/codespacemount/.persistedshare/docker-compose/docker-compose.devcontainer.build-1656605616368.yml -f /var/lib/docker/codespacemount/.persistedshare/docker-compose/docker-compose.devcontainer.containerFeatures-1656605684649.yml up -d --no-recreate
2022-06-30 16:24:18.875Z: Error: Command failed: docker-compose --project-name foo-dev_devcontainer -f /var/lib/docker/codespacemount/workspace/foo-dev/.devcontainer/docker-compose.yml -f /var/lib/docker/codespacemount/.persistedshare/docker-compose.codespaces.yml -f /var/lib/docker/codespacemount/.persistedshare/docker-compose/docker-compose.devcontainer.build-1656605616368.yml -f /var/lib/docker/codespacemount/.persistedshare/docker-compose/docker-compose.devcontainer.containerFeatures-1656605684649.yml up -d --no-recreate
2022-06-30 16:24:18.891Z:     at RR (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:204:2936)
2022-06-30 16:24:18.907Z:     at processTicksAndRejections (internal/process/task_queues.js:95:5)
2022-06-30 16:24:18.923Z:     at async PR (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:188:2240)
2022-06-30 16:24:18.942Z:     at async zR (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:245:2177)
2022-06-30 16:24:18.972Z:     at async nb (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:245:3110)
2022-06-30 16:24:18.995Z:     at async JR (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:245:13046)
2022-06-30 16:24:19.012Z:     at async KR (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:245:12802)
2022-06-30 16:24:19.030Z: Stop (10809 ms): Run: /usr/bin/node /usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /var/lib/docker/codespacemount/.persistedshare --container-data-folder .vscode-remote/data/Machine --container-system-data-folder /var/vscode-remote --workspace-folder /var/lib/docker/codespacemount/workspace/foo-dev --id-label Type=codespaces --log-level info --log-format json --config /var/lib/docker/codespacemount/workspace/foo-dev/.devcontainer/devcontainer.json --override-config /root/.codespaces/shared/merged_devcontainer.json --default-user-env-probe loginInteractiveShell --expect-existing-container --mount type=bind,source=/.codespaces/agent/mount/cache,target=/vscode --skip-post-create --update-remote-user-uid-default never --mount-workspace-git-root false
2022-06-30 16:24:19.048Z: Exit code 1
2022-06-30 16:24:19.064Z: Failed to create container.
2022-06-30 16:24:19.086Z: Error: Command failed: /usr/bin/node /usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /var/lib/docker/codespacemount/.persistedshare --container-data-folder .vscode-remote/data/Machine --container-system-data-folder /var/vscode-remote --workspace-folder /var/lib/docker/codespacemount/workspace/foo-dev --id-label Type=codespaces --log-level info --log-format json --config /var/lib/docker/codespacemount/workspace/foo-dev/.devcontainer/devcontainer.json --override-config /root/.codespaces/shared/merged_devcontainer.json --default-user-env-probe loginInteractiveShell --expect-existing-container --mount type=bind,source=/.codespaces/agent/mount/cache,target=/vscode --skip-post-create --update-remote-user-uid-default never --mount-workspace-git-root false
2022-06-30 16:24:19.102Z: Error Code: 1302
2022-06-30 16:24:19.120Z: Container creation failed.
2022-06-30 16:24:21.277Z: 
2022-06-30 16:24:21.297Z: Creating recovery container.

[GLStephen]

We are having similar weird issues with codespaces for the last few days. I suspect there is something infrastructure going on they have not noticed yet.

#19763

[peerkleio]

We are also having the same issue.

[rahularyan]

We are also seeing this issue since yesterday.

[eljog]

Thank you for the reports.
We see that specifying of devcontainer "features" when using Docker Compose is resulting in this problem. We are working on a fix for this issue.

[stevenramirezgains]

Is there a timeline here to recovery? We are seeing folks in our org be really slowed down by this issue.

[eljog]

We have identified a fix for this problem and I hope it can be rolled out by EOD tomorrow.
We hear the inconvenience faced by your developers and appreciate your patience.

[eljog]

Hi All,
This issue has been fixed. Please let us know if any issues persist.
Thank you for your patience.

[GLStephen]

@eljog an issue very similar to this appears to be happening, getting all sorts of notifications about not being able to "proxy" networking and similar messages like ports being already use when building and starting up containers.

This is very similar to the error we were getting during the issue above:

"Error response from daemon: driver failed programming external connectivity on endpoint CONTAINER_NAME (0fe94ef960e14fe9d3608e2d1c628925345fdb105c5ea9ae747d4df5bf982a1e): Error starting userland proxy: listen tcp4 0.0.0.0:8091: bind: address already in use"