☰

containerd -> dockerd

David Stark committed 2022-02-09 10:33:37 +0000 commit 8bd4c6dfd6f121b525b5575a015f363a1e7bab20

				compute/docker.md
			
          @@ -59,6 +59,6 @@ I don't know why, but sometimes (just sometimes) dockerd has problems creating i

           Check that 127.0.0.11 is listed in the container's resolv.conf as it should be, then check:  

           `nsenter -n -t $(docker inspect --format {{.State.Pid}} <container>) iptables -t nat -nvL`  

          -There should be two DNAT and two SNAT rules for port 53 (upd & tcp). If they're missing, you'll need to restart containerd to make it work.

          +There should be two DNAT and two SNAT rules for port 53 (upd & tcp). If they're missing, you'll need to restart dockerd to make it work.

           This only affects newly started containers - if DNS works at container-boot but fails later, it's something else.

...	...	@@ -59,6 +59,6 @@ I don't know why, but sometimes (just sometimes) dockerd has problems creating i
59	59
60	60	Check that 127.0.0.11 is listed in the container's resolv.conf as it should be, then check:
61	61	`nsenter -n -t $(docker inspect --format {{.State.Pid}} <container>) iptables -t nat -nvL`
62		-There should be two DNAT and two SNAT rules for port 53 (upd & tcp). If they're missing, you'll need to restart containerd to make it work.
	62	+There should be two DNAT and two SNAT rules for port 53 (upd & tcp). If they're missing, you'll need to restart dockerd to make it work.
63	63
64	64	This only affects newly started containers - if DNS works at container-boot but fails later, it's something else.