https://github.com/linux-system-roles/ee_linux_automation
Container image with related automation collections such as system roles, sap, mssql, and more
https://github.com/linux-system-roles/ee_linux_automation
Last synced: 12 months ago
JSON representation
Container image with related automation collections such as system roles, sap, mssql, and more
- Host: GitHub
- URL: https://github.com/linux-system-roles/ee_linux_automation
- Owner: linux-system-roles
- License: mit
- Created: 2021-11-30T21:49:10.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2025-07-17T03:17:17.000Z (12 months ago)
- Last Synced: 2025-07-17T06:03:41.317Z (12 months ago)
- Language: Dockerfile
- Size: 333 KB
- Stars: 4
- Watchers: 5
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# ee_linux_automation
[](https://quay.io/repository/linux-system-roles/ee_linux_automation)
Ansible supports a new feature for bundling collections and their runtime
environments, including the Ansible executable and dependencies, together in an
executable container. This is called an Ansible Execution Environment. This is
a [good introduction](https://www.ansible.com/blog/introduction-to-ansible-builder).
Linux System Roles is publishing an execution environment which contains
the following related collections and their dependencies:
* fedora.linux_system_roles
* sap.linux
* microsoft.sql
* freeipa.ansible_freeipa
`ee_linux_automation` uses the latest collections published in Galaxy, so if
you want to build an updated EE, you may have to first publish the latest
content in the collection. The EE version tag is
the version of the collection used to build - this is `$COLLECTION_VERSION`
below. Check the latest version e.g. for system roles:
https://galaxy.ansible.com/fedora/linux_system_roles. To build:
```
ansible-builder build -v 3 --container-runtime=podman \
--file=builder.yml --tag=ee_linux_automation:$COLLECTION_VERSION
podman images | grep ee_linux_automation
```
To publish to quay, you must have an auth token for your
`${XDG_RUNTIME_DIR}/containers/auth.json`. To obtain this token, login to your quay.io account,
go to `Account Settings`, go to `CLI Password: ` and click on `Generate
Encrypted Password`. Then use this with `podman login quay.io`.
```
podman tag ee_linux_automation:$COLLECTION_VERSION quay.io/linux-system-roles/ee_linux_automation:$COLLECTION_VERSION
podman push quay.io/linux-system-roles/ee_linux_automation:$COLLECTION_VERSION
```
To publish a testing image, use the `-testing` suffix:
```
podman tag ee_linux_automation:$COLLECTION_VERSION quay.io/linux-system-roles/ee_linux_automation:$COLLECTION_VERSION-testing
podman push quay.io/linux-system-roles/ee_linux_automation:$COLLECTION_VERSION-testing
```
Once you use `ansible-builder`, be sure to push the files in the `context/`
directory as well. These are the files that can be used by `podman build`
or by the `quay.io` builder. If you just want to update the
context files, you can use `ansible-builder create` instead of `ansible-builder
build`, then submit a PR for the updated files.