ContainerCraft / ContainerCraft/devcontainer

Devcontainer started failing upon codespaces creation

Ouverte
#12 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Dockerfile
Étoiles
43
Forks
3
Métriques de merge des PR
Aucune PR mergée en 30 j

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

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
docker, github
Domaine
cloud, devops
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.