containers.podman.buildah connection – Interact with an existing buildah container
Note
This connection plugin is part of the containers.podman collection (version 1.19.0).
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install containers.podman.
To use it in a playbook, specify: containers.podman.buildah.
Synopsis
Run commands or put/fetch files to an existing container using buildah tool.
Supports container building workflows with enhanced error handling and performance.
Parameters
Parameter |
Comments |
|---|---|
Automatically commit changes after successful operations. Choices:
Configuration:
|
|
Executable for buildah command. Default: Configuration:
|
|
Extra arguments to pass to the buildah command line. Default: Configuration:
|
|
Timeout in seconds for container operations. 0 means no timeout. Default: Configuration:
|
|
Additional environment variables to set in the container. Default: Configuration:
|
|
Continue with copy operations even if container mounting fails. Choices:
Configuration:
|
|
Enable automatic detection and use of container mount points for file operations. Choices:
Configuration:
|
|
The ID or name of the buildah working container you want to access. Default: Configuration:
|
|
User specified via name or UID which is used to execute commands inside the container. For buildah, this affects both run commands and copy operations. Configuration:
|
|
Set working directory for commands executed in the container. Configuration:
|
Note
Configuration entries listed above for each entry type (Ansible variable, environment variable, and so on) have a low to high priority order. For example, a variable that is lower in the list will override a variable that is higher up. The entry types are also ordered by precedence from low to high priority order. For example, an ansible.cfg entry (further up in the list) is overwritten by an Ansible variable (further down in the list).