`sudo usermod -aG docker pi` doesn't persist

[fcaraujo]

Hi Sakaki,

Firstly thanks for your awesome contribution and your time as well.

I just followed your tutorial here installing raspbian-nspawn-64 and docker.

So I noticed after run sudo usermod -aG docker pi I still get permission denied, even after a reboot/retry.
Would you have any suggestion?

Thanks!

pi@debian-buster-64:~ $ sudo usermod -aG docker pi
pi@debian-buster-64:~ $ docker info
Client:
 Debug Mode: false

Server:
ERROR: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.40/info: dial unix /var/run/docker.sock: connect: permission denied
errors pretty printing info
pi@debian-buster-64:~ $

[sakaki-]

31 Oct 2020: sadly, due to legal obligations arising from a recent change in my 'real world' job, I must announce I am standing down as maintainer of this project with immediate effect. For the meantime, I will leave the repo up (for historical interest, and since the Debian package is still in the official Raspbian repos); however, there will be no further updates to the underlying OS images etc., nor will I be accepting / actioning further pull requests or bug reports from this point. Email requests for support will also have to be politely declined, so, please treat this as an effective EOL notice.

For further details, please see my post here.

With sincere apologies, sakaki ><

[kj5wi]

I have the same issue here. Looks like the problem resides in the way debian-buster-64 is created. As long as a reboot is not used, a simple logout/login within the container will get docker group into user pi. Ive read many docs, but am still looking for how user pi is set up when the deb container is reloaded.