Ansible Role: serdigital64.container.cnt_podman¶
Purpose¶
Manage provisioning of Podman.
Supported features in the current version:
- Deploy application. Packages are defined in the variable
cnt_podman_profiles.
The cnt_podman Ansible-Role is part of the A:Platform64 project and is available in the container Ansible-Collection.
Usage¶
The following example is an Ansible Playbook that includes all the supported features:
use this link if viewing the doc on github
---
- name: "Container / Podman / Usage example"
hosts: "localhost"
gather_facts: true
tasks:
- name: "Example: Install Podman"
vars:
cnt_podman:
resolve_prereq: true
deploy: true
ansible.builtin.include_role:
name: "serdigital64.container.cnt_podman"
...
The playbook can be run by executing:
# Set ANSIBLE_COLLECTIONS_PATHS to the default location. Change as needed.
ANSIBLE_COLLECTIONS_PATHS="${HOME}/.ansible/collections"
ansible-playbook "${ANSIBLE_COLLECTIONS_PATHS}/ansible_collections/serdigital64/container/playbooks/cnt_podman.yml"
Role Parameters¶
Actions¶
- Use action-parameters to control what tasks are enabled for the role to execute.
- Parameters should be declared as task level vars as they are intented to be dynamic.
cnt_podman:
resolve_prereq:
deploy:
| Parameter | Required? | Type | Default | Purpose / Value |
|---|---|---|---|---|
| cnt_podman.resolve_prereq | no | boolean | false | Enable automatic resolution of prequisites |
| cnt_podman.deploy | no | boolean | false | Enable installation of application packages |
End State¶
- Use end-state parameters to define the target state after role execution.
- Parameters should be declared in host_vars or group_vars as they are intended to be permanent.
cnt_podman_application:
name:
type:
version:
installed:
| Parameter | Required? | Type | Default | Purpose / Value |
|---|---|---|---|---|
| cnt_podman_application | no | dictionary | Set application package end state | |
| cnt_podman_application.name | no | string | "podman" | Select application package name |
| cnt_podman_application.type | no | string | "distro" | Select application package type |
| cnt_podman_application.version | no | string | "latest" | Select application package version |
| cnt_podman_application.installed | no | boolean | true | Set application package end state |
Deployment¶
OS Compatibility¶
The operating system compatibility list is defined in the variable: cnt_podman_platforms
Dependencies¶
- Ansible Collections:
- serdigital64.backup
- bkp_archive
- serdigital64.system
- sys_package
- sys_repository
- serdigital64.backup
Prerequisites¶
The Ansible engine must be already installed and configured for privileged access and remote execution.
In addition the following prerequisites can be automatically solved when running the playbook by setting the role action: resolve_prereq: true
- Package manager for the target application is installed and enabled.
Installation Procedure¶
Manually install Ansible Collections from the Ansible Galaxy repository:
ansible-galaxy collection install --upgrade serdigital64.container
Automatic installation is also available by deploying A:Platform64
Contributing¶
Help on implementing new features and maintaining the code base is welcomed.
Please see the guidelines for further details.