Debian 13 Trixie DNS Resolution failure - empty container resolv.conf upon restart with host using DHCP
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 38/100
- Tipo de issue
- Bug
- Clareza
- Razoavelmente clara
- Status de atividade
- Estagnada
- Stack de tecnologia
- debian, docker
- Domínio
- devops, networking
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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.
- Linguagem predominante
- Dockerfile
- Estrelas
- 37
- Forks
- 42
- Merge médio
- 16h 53min
- PRs com merge (30d)
- 30
Preparar o ambiente
- Inclui um Dockerfile ou arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de docker/packaging
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 62/100
docker/packaging#586 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 65/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 48/100
docker/packaging#558 · 1 reação ·
Mantenedores costumam responder em até 1 dia
-
docker-ce is unable to be installed on UBI 10 container images because iptables-nft is not availableAberta
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 52/100
Mantenedores costumam responder em até 1 dia
Todas as issues de docker/packaging
Issues semelhantes
-
bot:ai-assisted component:platform-js status:untriaged
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
midnightntwrk/platform-js#69 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Netcracker/qubership-authz-agent#311 ·
Mantenedores costumam responder em até 1 dia
-
Falló el respaldo diarioAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
manuXD270516/descanso#80 ·
Mantenedores costumam responder em até 2 dias
-
Status: Triage Type: Enhancement
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
canonical/alertmanager-k8s-operator#504 ·
Mantenedores costumam responder em até 2 dias
-
deferred tooling
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
mauwii/pokerchipcase#157 ·
Mantenedores costumam responder em até 1 dia