Does not work if there is no `docker` group about cri-dockerd HOT 9 OPEN

Should have mentioned I didn't yet install it :) probably makes sense to do that before installing the cri.

from cri-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.

from cri-dockerd.

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)

https://packages.ubuntu.com/jammy/docker.io

from cri-dockerd.

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.

from cri-dockerd.

This is probably something to speak to the snap maintainer about. How do users get permissions to run docker commands with the snap?

from cri-dockerd.

@evol262 Good point. That's an issue you can raise over at snap

from cri-dockerd.

FYI this happened to me as well on ubuntu 20.04, I had to add group docker (no snap installation)

from cri-dockerd.

How did you install docker? The (deb) packages should have added the "docker" group

from cri-dockerd.

It seems that the cri-dockerd packages have a dependency on containerd instead of dockerd...

from cri-dockerd.