geerlingguy / ansible-role-docker

Ansible Role - Docker
https://galaxy.ansible.com/geerlingguy/docker/
MIT License
1.81k stars 853 forks source link

Rootless docker #413

Closed reboss closed 1 month ago

reboss commented 1 year ago

Here is a fairly complete "Rootless Docker" setup.

One can toggle between both root Docker and rootless Docker by re-running the role with docker_rootless set to either true or false

I maintain idempotency when running command tags so that we don't run the docker-rootless-setuptool.sh < install | uninstall > unnecessarily.

There are a couple things that I didn't get to, and don't see much value in solving for this PR:

  1. This code doesn't support rootless docker in RHEL/CentOS 7 because both are end of life and I feel like trying to get them to work may overcomplicate the code a bit.
  2. I chose not to install fuse-overlayfs, or any of its counterparts, despite it being recommended by the docs. Once again, I feel like this would have overcomplicated things a bit. It's only recommended Docker, and not a strict dependency anyways.

Ultimately, I have tested this thoroughly on Ubuntu and it should work on the latest version of RHEL, however I can't test because I don't have a RHEL subscription.

I'd say having this support one OS, is better than supporting none. Let me know if you'd like any changes made, @geerlingguy

Fixes #412

Update: I've confirmed that this process works on CentOS Stream 9

joshavant commented 8 months ago

Just commenting that I'd be excited for this to get merged into main.

Is there an easy answer to what's left on this and what it needs to get merged into main? @geerlingguy @paranerd @egdoc

github-actions[bot] commented 3 months ago

This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

github-actions[bot] commented 1 month ago

This pr has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.