Docker issue while connecting with containerD on live server

[rimelek (Ákos Takács)]

@priyanshiwebelight

Logs also showed some issues related to DNS like this →
“No non-localhost DNS nameservers are left in resolv.conf. Using default external servers”

“failed to query external DNS server” client-addr=“udp:127.0.0.1:55812” dns-server=“udp:127.0.0.53:53” error=“read udp 127.0.0.1:55812->127.0.0.53:53: i/o timeout” question=“;[example.domain.com](http://example.domain.com/).\tIN\t AAAA”"

I wrote about that prt here:

VM Migration with Pre-installed Docker Results in Slow Performance

It is a little bit more complicated. I remembered it copied the resolv.conf to the docker data root for the new container and mounted that copy, except when it was the stub resolver, because it always mounts something that should work in a container. Testing that now, I see that when I have systemd and I use the stub resolver, it mounts /run/systemd/resolve/resolv.conf and I see this in the logs: Apr 09 18:53:52 docker-vm-noble dockerd[3887]: time="2025-04-09T18:53:52.799236585+02:00" level=i…

@priyanshiwebelight

“failed to create network gitlab-docker_default: Error response from daemon: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o br-bf92dde6e60e -j DOCKER: iptables v1.8.10 (nf_tables): Chain ‘DOCKER’ does not exist
Try iptables -h’ or ‘iptables --help’ for more information.
(exit status 2)”

It could indicate something similar to this:

Docker failing to create IP table rules

Thank you. sorry for the slow response. So we know now that you are using the official Docker CE on Ubuntu 22.04. That should work. There are newer versions which you can install to see if it was fixed. 28.0.4 is the latest. I tested only on Ubuntu 24.04. You could also check if you have an uptodate iptables. But I think the error means that the DOCKER-FORWARD chain is missing from the rules so it cannot be updated when you add a new docker network and Docker Compose does it. The chain can be m…

Make sure there is nothing else managing iptables rules

@priyanshiwebelight

I checked the logs deeply and I believe the main cause of issue is this → “Failed to retrieve containerd version”

I don’t have a link for that, but the following is just a warning

@priyanshiwebelight

WARN[0000] containerd config version `1` has been deprecated and will be converted on each startup in containerd v2.0, use `containerd config migrate` after upgrading to containerd 2.0 to avoid conversion on startup

You can probably ignore that. I wrote about that here:

Containerd config version `1` has been deprecated and will be converted on each startup in containerd v2.0, use `containerd config migrate` after upgrading to containerd 2.0 to avoid conversion on startup

Where did you get this error message? The latest containerd is 1.7.23. Containerd v2 is just a release candidate: Release containerd 2.0.0-rc.5 · containerd/containerd · GitHub I have an even newer containerd version as my Docker version is newer too and I haven’t seen this error message anywhere. update: Okay, I found it in journal logs. I think you can safely ignore that message. You could use containerd without Docker but Docker will take care updating containerd or if anything will need …

If the containerd version could not be retrieved, I guess containerd is failing so you could not even run

containerd --version

Or did you do that before you shared the version at the beginning of your message?
I’m not sure it is related, but your quoted error messge looks like single line. Was it reall a single line?

@priyanshiwebelight

msg=“Ignoring extra error returned from registry” error=“unauthorized: authentication required”