-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question regarding Podman compatibility? #10
Comments
What kind of changes would it entail? I have to admit I still don't use Podman much myself at this time. |
- Fixes the problem described in geerlingguy#10
I made the PR in #11 but am not sure if everything continues to work in Docker. I made it look like your Debian image. Especially, |
Podman support would be great. |
Hey @c-goes @jwillikers @geerlingguy I've been using this container image to test a PR in the I'm using an M1 MacBook so I installed Podman via
I've then installed
Here is my ---
role_name_check: 1
dependency:
name: galaxy
driver:
name: podman
platforms:
- name: instance
image: geerlingguy/docker-ubuntu2004-ansible
tmpfs:
- /run
- /tmp
volumes:
- /sys/fs/cgroup:/sys/fs/cgroup:ro
capabilities:
- SYS_ADMIN
command: "/lib/systemd/systemd"
pre_build_image: true
provisioner:
name: ansible
playbooks:
converge: ${MOLECULE_PLAYBOOK:-converge.yml}
|
Hello
Would you accept a PR to make this image compatible with rootless podman?
I realized that your Debian 10 image works without issues but this one does not. Discussion is here
containers/podman#8545 (comment)
This issue is probably caused by the VOLUMES in this repo's Dockerfile.
The text was updated successfully, but these errors were encountered: