Replies: 1 comment
-
the DIND container runs containerd as a child-process that's started by the dockerd daemon; this allows docker to run in situations where no init-manager is present, and for manually starting To configure containerd for other purposes, such as to use it as runtime for k8s, containerd must be started independently, and the docker daemon to be configured to with the path to the containerd API socket; this is what's done when docker is running as a systemd service (in which case containerd is running as a separate service); moby/contrib/init/systemd/docker.service Line 13 in ef15c13 I do have a draft PR (but it looks like it bit-rot) to also allow a custom configuration file to be used when running containerd as a child-process, but there was no consensus on that yet (and I'd have to dust it off to bring it in a mergeable state again), and a proposal to make containerd (when run as a child-process) closer to how it would run as a standalone service; |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm looking for the ability to configure a containerd registry mirror. I'm currently using the docker:28.1.1-dind image and have the
--cri-containerd
flag enabled, but how can I adjust the plugins and config?From the logs I can see
I tried baking in a custom
containerd.toml
with read-only access, but that fails withfailed to start containerd: failed to open containerd config file (/var/run/docker/containerd/containerd.toml): open /var/run/docker/containerd/containerd.toml: read-only file system
Desired containerd.toml
Example hosts.toml
Am I missing something obvious?
Beta Was this translation helpful? Give feedback.
All reactions