Debian 13 Trixie DNS Resolution failure - empty container resolv.conf upon restart with host using DHCP
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 38/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- debian, docker
- 领域
- devops, networking
调研方向
Start by reading the Docker packaging repository’s systemd service configuration and the Debian 13 startup sequence described in the issue. Reproduce a reboot with DHCP and check when Docker starts relative to network configuration and when container resolv.conf is generated. Done means containers started after reboot have working DNS without a manually added delay service.
由索引模型根据 Issue 内容生成。
描述
I've been trying to debug an issue I'm having on fresh Debian 13 Trixie installs (I've not noticed it on upgrade). Having installed Docker via the official Docker repository as outlined in the instructions, I then set up some compose stacks with containers using unless-stopped for restart. My docker host uses DHCP and successfully connects, but it appears the Docker Engine is grabbing the host's /etc/resolv.conf too early. Looking in the container, I see this:
# Generated by Docker Engine.
# This file can be edited; Docker Engine will not make further changes once it
# has been modified.
# Based on host file: '/etc/resolv.conf'
# Overrides: []
If I, however, restart the container once the host is up, this populates as expected and I have no DNS resolution issues. I see a thread about the exact problem on the Docker forums and a note there suggesting an issue be opened against the packaging repository for it. I didn't see such an issue already (if I missed it, I apologize), so I am creating this one for the issue. I can easily recreate the issue at-will, so can capture thinks or try tweaks as others may suggest.
Looking at my system journal, I do indeed see docker starting up before dhcpd assigned an IP and DNS addresses with it.
May 01 22:03:01 docker3 systemd[1]: Started docker.service - Docker Application Container Engine.
May 01 22:03:01 docker3 systemd[1]: Reached target multi-user.target - Multi-User System.
May 01 22:03:01 docker3 systemd[1]: Reached target graphical.target - Graphical Interface.
May 01 22:03:01 docker3 systemd[1]: Startup finished in 1.569s (kernel) + 4.942s (userspace) = 6.511s.
...
May 01 22:03:04 docker3 ifup[650]: ens18: leased ##snipped## for 86400 seconds
For the time being, I used the suggested wait service to force a few second delay (I had to add the wait service to docker.service) so that it comes up after dhcpd has done its work.
- 主要语言
- Dockerfile
- 星标
- 37
- 派生
- 42
- 平均合并
- 16 小时 53 分钟
- 30 天内合并 PR
- 30
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
docker/packaging 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
docker/packaging#586 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 65/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
docker/packaging#558 · 1 个 reaction ·
维护者通常 1 天内回复
-
docker-ce is unable to be installed on UBI 10 container images because iptables-nft is not available未关闭
难度 3/5 1-2 天 新手友好度 52/100
维护者通常 1 天内回复
相似的 Issue
-
breaking change
难度 1/5 1 小时以内 新手友好度 84/100
it-at-m/lhm_actions#441 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
tchiotludo/akhq#3438 ·
维护者通常 1 天内回复
-
good first issue help wanted security
难度 2/5 1-3 小时 新手友好度 82/100
gsel001/one-meal-forward#22 ·
-
Run the race detector on internal/restapi in CI可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
OneBusAway/maglev#2135 ·
维护者通常 2 天内回复
-
priority/medium status/ready type/chore
难度 2/5 1-3 小时 新手友好度 84/100
discobox-ai/discobox#1357 ·
维护者通常 1 天内回复