ansible-podman-collections
patchew
ansible-podman-collections | patchew | |
---|---|---|
4 | 1 | |
244 | 68 | |
2.5% | - | |
8.5 | 10.0 | |
12 days ago | about 1 year ago | |
Python | Python | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ansible-podman-collections
-
Make systemd better for Podman with Quadlet
I'm using the podman ansible module[1] to manage the podman container atm, it's ... Okish. I wrote a spaghetti mess with ansible conditionals and loops to manage multitude of systemd files made from podman-generate-systemd. If I had some time maybe I'll try this out, a more declarative approach would certainly be nicer.
[1]: https://github.com/containers/ansible-podman-collections
-
The Bullhorn #82 (Ansible Newsletter)
New version 1.10.0 of Ansible Podman collection was released. We have a lot of bugfixes and improvements, a new become plugin - podman_unshare which allows user to execute commands in its container user namespace, and a new module - podman_generate_systemd for Systemd unit files generation for containers and pods.
-
The Bullhorn #42 (Ansible Newsletter)
containers.podman collection released new 1.9.1 version, since last update we have new podman_tag module, also updated module podman_secret which manages secrets for Pods and options for newest Podman Pod versions.
-
How to debug change detection?
use the source: https://github.com/containers/ansible-podman-collections
patchew
-
Make systemd better for Podman with Quadlet
I do something similar but I don't use podman-generate-systemd; instead I create the systemd service by hand using a Jinja template[1], and then start the service[2]. This has the advantage that there's no hole where the container is running but systemd configuration has not been updated yet.
Either way, it's indeed quite tempting to replace the nasty templates that build the podman commandline with quadlet.
[1] https://github.com/patchew-project/patchew/blob/master/scrip...
[2] https://github.com/patchew-project/patchew/blob/master/scrip...
What are some alternatives?
meetup - The regular Ansible Community Meetup
podman - Management of podman, including systemd services that use podman
community.network - Ansible Community Network Collection
udocker - A basic user tool to execute simple docker containers in batch or interactive systems without root privileges.
ovirt-ansible-collection - Ansible collection with official oVirt modules and roles
foreman-ansible-modules - Ansible modules for interacting with the Foreman API and various plugin APIs such as Katello
ansible-requirements-updater - Update your requirements.yml with this grisly Ansible playbook.
ansible-collection-icinga-director - An Ansible collection that contains modules to change objects in Icinga 2 using the director API.
galactory - An Ansible Galaxy proxy for Artifactory
sensu-go-ansible - Official Ansible module for Sensu Go
toolbox-desktop-integration
community.crypto - The community.crypto collection for Ansible.