ContainerCraft / ContainerCraft/devcontainer

Devcontainer started failing upon codespaces creation

Open
#12 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Dockerfile
Stars
43
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Sync my local copy with `main`. When I open a codespace using the `konductor` devcontainer, I get booted into a recovery container due to a failed devcontainer build.

```
2025-03-06 21:15:22.608Z: [2025-03-06 21:15:22] Running as user: ubuntu (current: ubuntu)
2025-03-06 21:15:22.614Z: [2025-03-06 21:15:22] Saving environment variables to /home/ubuntu/.env
2025-03-06 21:15:22.664Z: Shell server terminated (code: 126, signal: null)
2025-03-06 21:15:22.665Z: {"outcome":"error","message":"An error occurred setting up the container.","description":"An error occurred setting up the container.","containerId":"df41e9a46ae0afeda4357ea2dfdf2f00739559d64d6b93cd657360bce508f424"}
2025-03-06 21:15:22.665Z: unable to find user vscode: no matching entries in passwd file
2025-03-06 21:15:22.667Z: Error: An error occurred setting up the container.
```

The full log's here: https://gist.github.com/sourishkrout/595ee0cf08ea49459c0084bf4cfdf88e

Contributor guide

Open the contributing guide

Research direction

Start with the linked full log and the konductor devcontainer used during Codespaces creation, then inspect the configuration responsible for the failed build. Reproduce the failure and verify that the devcontainer builds successfully and opens a Codespace without falling back to recovery.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, github
Domain
cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.