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

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

オープン
#107 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
主要言語
Bicep
スター
72
フォーク
859
平均マージ
2日 9時間
マージ済み PR(30日)
6

説明

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)

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

starter-no-infra ブランチを使用し、まずリポジトリの devcontainer と Docker Compose の設定を調査します。Redis と PostgreSQL のイメージが pull された後のコンテナ起動に焦点を当て、docker compose up で失敗を再現します。新しい GitHub Codespace がリカバリーモードや報告された OCI runtime error なしで正常に起動すれば完了です。

索引モデルが issue の本文から書いたものです。

評価

技術スタック
django, docker, docker-compose, postgresql, python, redis
領域
backend, databases, devops, infrastructure
issue の種類
バグ
難易度
3/5
見積もり時間
1〜2日
活発さ
静か
明瞭さ
おおむね明確
初心者へのやさしさ
48/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。