Open MikeSpreitzer opened 2 years ago
I don't think it has been tested with anything, except for the regular installation from a deb.
https://docs.docker.com/engine/install/ubuntu/
It might be supported with "docker.io", not sure ? (system, as in sudo apt install docker.io
)
If it comes to it, it would be possible to remove "cri-docker.socket" and modify "cri-docker.service" to run without it.
Requires=cri-docker.socket
ExecStart=/usr/bin/cri-dockerd --container-runtime-endpoint fd:// --network-plugin=
That would make cri-dockerd
start on boot, and not on demand, but might work better with odd docker installations.
This is probably something to speak to the snap
maintainer about. How do users get permissions to run docker
commands with the snap?
@evol262 Good point. That's an issue you can raise over at snap
FYI this happened to me as well on ubuntu 20.04, I had to add group docker (no snap installation)
How did you install docker? The (deb) packages should have added the "docker" group
Should have mentioned I didn't yet install it :) probably makes sense to do that before installing the cri.
It seems that the cri-dockerd packages have a dependency on containerd instead of dockerd...
Yes, they do, which is typically provided by docker. The reason there isn't a dependency on Docker is that there is no metapackage/requirement shared by docker-ce/docker-ee/docker-io/etc. We could at least create the group if it isn't present, because cri-docker.service
depends on docker.service (which is consistent across packages), which still provides a runtime dependency.
I just installed Ubuntu 22.04 server on a new VM. The install process offered to "install" "docker", and I took the offer. Later I found out this install was done with
snap
. It turns out thatsnap install docker
, at least on Ubuntu 22.04, does NOT create a usergroup nameddocker
. But thecri-docker.socket
systemd unit here assumes the existence of such a group.