Debian 13 Trixie DNS Resolution failure - empty container resolv.conf upon restart with host using DHCP

Ouverte
#597 4 commentaires 5 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
38/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
debian, docker
Domaine
devops, networking

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Dockerfile
Étoiles
37
Forks
42
Merge moyen
16 h 53 min
PR mergées (30 j)
30

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de docker/packaging

Toutes les issues de docker/packaging

Issues similaires

Plus d'issues DevOps

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.