https://bugzilla.suse.com/show_bug.cgi?id=1224066 https://bugzilla.suse.com/show_bug.cgi?id=1224066#c6 Martin von Reichenberg changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #6 from Martin von Reichenberg --- (In reply to Aleksa Sarai from comment #5)

(In reply to Alexandre Vicenzi from comment #3)

...

There is official documentation that describes manual steps post-install on Linux, see https://docs.docker.com/engine/install/linux-postinstall/.

I don't classify this as a bug, but rather well-known behavior. Changes to the Docker package would be a feature request.

Aleksa, should we add users to groups in %post/%posttrans scripts?

Access to the docker group gives you admin privileges to the machine (it is trivial to get root host access using Docker) and so automatically adding users seems like a bad idea in general. We also don't know which users we should add to the group at install time anyway.

(In reply to Martin von Reichenberg from comment #2)

...

So the point is that there is no mention (the one similar to VirtualBox) about the current user is supposed to be part of the Docker group which could easily be set in %post / %posttrans script as: `usermod -aG $USER docker` (or equivalent...).

(In reply to Martin von Reichenberg from comment #4)

...

But it is a formerly missing information by those who maintain it - As a post installation step / notification about what needs to be done in order to use the software.

I don't see anything in the VirtualBox spec file which would tell users about the vboxusers group at install time. If you want, we can add a line in the package documentation about the docker group, but the fact that you need to be part of the docker group to administer Docker is incredibly common knowledge for users of Docker. As mentioned above, this is mentioned already by the upstream documentation.

VirtualBox shows the notification window at the initial runtime. In case of DistroBox it is not clear at the very first usage that it's all bound to Docker (- services/groups). Probably an echo/printf message could be enough, but it should be told after install or initial startup somehow - more likely a request to upstream. -- You are receiving this mail because: You are on the CC list for the bug.