Open antage opened 2 years ago
Docker must be able to manage net namespaces to work (unless you start every container with --network=host
which I guess is not your use case). Thus Docker daemon itself cannot be in a net namespace.
There are a few workarounds I can think of:
docker pull
, and make all traffic from that proxy go through a net namespaceI'll leave this issue open to see if anyone comes with a better idea.
Did anyone try to run
docker.service
/containerd.service
withsystemd-named-nets
in own namespace?I tried and commands like
docker pull
works fine butdocker run
can't start any container.I hope someone knows a fix.