Azure-Samples / Azure-Samples/msdocs-django-postgresql-sample-app

Codespace consistently fails to create devcontainer with UnifiedContainersErrorFatalCreatingContainer (1302) on starter-no-infra branch

Offen
#107 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Bicep
Sterne
72
Forks
859
Ø Merge
2 T. 9 Std.
Gemergte PRs (30 T.)
6

Beschreibung

Creating a new GitHub Codespace for the Django PostgreSQL sample application consistently fails during devcontainer startup.

The Docker image builds successfully, but one container fails to start with an OCI runtime error. The Codespace then enters recovery mode.

The issue is reproducible every time.

Repository

Azure-Samples/msdocs-django-postgresql-sample-app

Branch:

starter-no-infra

Steps to Reproduce
Open the repository:
[https://github.com/Azure-Samples/msdocs-django-postgresql-sample-app](https://github.com/Azure-Samples/msdocs-django-postgresql-sample-app?utm_source=chatgpt.com)
Select the starter-no-infra branch.
Create a new GitHub Codespace.
Wait for the devcontainer to finish building.

Steps to Reproduce
Open the repository:
[https://github.com/Azure-Samples/msdocs-django-postgresql-sample-app](https://github.com/Azure-Samples/msdocs-django-postgresql-sample-app?utm_source=chatgpt.com)
Select the starter-no-infra branch.
Create a new GitHub Codespace.
Wait for the devcontainer to finish building.
Expected behavior

The Codespace should finish creating successfully and open VS Code with the development environment ready.

Actual behavior

The build completes successfully, but Docker Compose fails while starting the containers.

The Codespace then fails with:

UnifiedContainersErrorFatalCreatingContainer
Error code: 1302

Recovery container is created instead of the intended development container.

Relevant log
Error response from daemon:
failed to create task for container:
failed to create shim task:
OCI runtime create failed:
runc create failed:
unable to start container process:
can't get final child's PID from pipe: EOF

runc init error(s):
nsexec-1: failed to open /proc/.../ns/net: No such file or directory
nsexec-0: failed to sync with stage-1

What I've tried
Deleted and recreated the Codespace multiple times.
Deleted and recreated the fork.
Tried both:
the original repository
my fork
Did not modify any files before the failure occurred.
The issue happens immediately after Codespace creation.
A different test repository creates a Codespace successfully, suggesting the issue is specific to this repository/devcontainer.
Environment
GitHub Codespaces
Repository: Azure-Samples/msdocs-django-postgresql-sample-app
Branch: starter-no-infra
Browser: Google Chrome
Operating System: Windows 11
Additional information

The Docker image itself appears to build successfully. The failure occurs during docker compose up, after the Redis and PostgreSQL images have been pulled and the network and volumes have been [created.

[Pasted text(6).txt](https://github.com/user-attachments/files/29376326/Pasted.text.6.txt)

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Use the starter-no-infra branch and inspect the repository's devcontainer and Docker Compose configuration first. Reproduce the failure with docker compose up, focusing on the container startup after the Redis and PostgreSQL images are pulled; done means a new GitHub Codespace starts successfully without recovery mode or the reported OCI runtime error.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
django, docker, docker-compose, postgresql, python, redis
Bereich
backend, databases, devops, infrastructure
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Ruhig
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
48/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.