Skip to content

docs: build your own RTE from the published RTE layers #34

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.

Sign up for GitHub

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

Merged
blaipr merged 1 commit into from
Oct 12, 2026
Merged

docs: build your own RTE from the published RTE layers #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,8 @@ AnsibleForms 7 runs no playbook in the app: the `rte` container runs them, from

`data/seed.yaml` registers it as the default runner on every start, so it is read-only under Connections > Runners.
Ansible settings, roles and collections under `data/ansible/` are mounted into the RTE, not the app. When your
playbooks need more, build an image from the app's `Dockerfile.rte` and point the `rte` service at it.
playbooks need more, build an image FROM `ansibleforms-rte-core` or `ansibleforms-rte-full` and point the `rte` service
at it: the app's [examples/rte](https://github.com/ansibleforms/ansibleforms/tree/main/examples/rte) shows how.

## Kubernetes

Expand Down
Loading