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 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Bicep
星标
72
派生
859
平均合并
2 天 9 小时
30 天内合并 PR
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 配置。使用 docker compose up 重现故障,重点关注拉取 Redis 和 PostgreSQL 镜像后的容器启动;当新的 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 摘要。