Have you a better solution now, than just being heavy handed chown and chmod?
Another workaround that I’ve tried is using sudo
on Docker commands that need to access /etc/docker
. This allows the torizon
user to access /etc/docker
in the scope of a single command without needing to change the permissions of any files or directories.
So for example to login:
sudo docker --config /etc/docker login
Then to pull your image from your private registry:
sudo docker --config /etc/docker pull <your container image>
Best Regards,
Jeremias