# No local doc about execution-environment.yml

**URL:** <https://forum.ansible.com/t/no-local-doc-about-execution-environment-yml/45629>\
**Category:** Get Help\
**Tags:** fedora, ansible-builder\
**Created:** [April 3, 2026, 6:25am UTC](https://forum.ansible.com/t/no-local-doc-about-execution-environment-yml/45629 "2026-04-03T06:25:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nickhardiman](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nickhardiman/32/315_2.png) [@nickhardiman](https://forum.ansible.com/u/nickhardiman)\
**Post date:** [April 3, 2026, 6:25am UTC](https://forum.ansible.com/t/no-local-doc-about-execution-environment-yml/45629/1 "2026-04-03T06:25:35Z")

</div>

**No local guide to writing execution-environment.yml**.

Possible I didn’t see what was right in front of my face here, just checking -

Is there a local guide to writing _ansible-builder_’s config file `execution-environment.yml`?

(As in a file on my machine provided by the package, not on a remote website)

I can’t find anything about the content of ansible-builder’s config file on my Fedora install. No man page, no commented example in /etc/ or /usr/share/doc/, no copy of [Execution environment definition — Ansible Builder Documentation](https://docs.ansible.com/projects/builder/en/latest/definition/), and no pointers given by ansible-builder -h.

---

<div class="post-metadata">

**Author:** ![taylorbrooks](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/taylorbrooks/32/10499_2.png) [@taylorbrooks](https://forum.ansible.com/u/taylorbrooks)\
**Post date:** [April 3, 2026, 7:48pm UTC](https://forum.ansible.com/t/no-local-doc-about-execution-environment-yml/45629/2 "2026-04-03T19:48:35Z")

</div>

Have you tried checking your configuration settings for this? A few things that commonly cause this type of issue:

1. Check if there are any recent updates or changes to your setup that might have triggered this behavior.

2. Look at the logs for any error messages around the time this started happening. The specific error codes will point you to the root cause faster than guessing.

3. If you are self-hosting, make sure your environment variables and config files are properly set. Sometimes a missed setting after an upgrade causes exactly this kind of problem.

What version are you running, and did this start after a specific change?

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [April 4, 2026, 9:01am UTC](https://forum.ansible.com/t/no-local-doc-about-execution-environment-yml/45629/3 "2026-04-04T09:01:30Z")

</div>

@taylorbrooks your answer has nothing to do with the question. Did you maybe add it the wrong thread?

---

<div class="post-metadata">

**Author:** ![RianKellyIT](https://avatars.discourse-cdn.com/v4/letter/r/edb3f5/32.png) [@RianKellyIT](https://forum.ansible.com/u/RianKellyIT)\
**Post date:** [April 4, 2026, 9:28pm UTC](https://forum.ansible.com/t/no-local-doc-about-execution-environment-yml/45629/4 "2026-04-04T21:28:50Z")

</div>

The ansible-builder package does not ship man pages or local documentation files on Fedora. This is a known gap - the tooling follows Python project conventions where docs live online rather than being bundled with the package.

A few workarounds for offline or local reference:

Check what files come with the package:

rpm -ql python3-ansible-builder | grep -i doc

This often returns nothing meaningful, but it confirms what is bundled.

For the execution-environment.yml schema, you can find it in the installed package source:

python3 -c “import ansible\_builder, os; print(os.path.dirname(ansible\_builder. **file** ))”

Navigate to that directory and look for schema files or YAML examples under the v3/ subdirectory.

The example files from the upstream repository are the most comprehensive reference if you download them:

pip download ansible-builder --no-deps -d /tmp/ab\_pkg  
cd /tmp/ab\_pkg && unzip \*.whl -d ab\_extracted

Inside you will find the package source including schema definitions and any bundled examples.

For reverse-engineering the format without internet access: run ansible-builder create with a minimal EE definition. It generates a Containerfile that documents which fields were interpreted and how they map to the container build steps.

---

<div class="post-metadata">

**Author:** ![nickhardiman](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nickhardiman/32/315_2.png) [@nickhardiman](https://forum.ansible.com/u/nickhardiman)\
**Post date:** [April 8, 2026, 2:06pm UTC](https://forum.ansible.com/t/no-local-doc-about-execution-environment-yml/45629/5 "2026-04-08T14:06:56Z")

</div>

Thanks for that.

Selecting bits from the [schema file](https://github.com/ansible/ansible-builder/blob/devel/src/ansible_builder/ee_schema.py) get me closer.

(This is from the _ansible-builder-3.1.0-6.fc43.rpm_ package in the fedora repo, not python3-ansible-builder).

```auto
# grep -e '^schema' -e '^ "' /usr/lib/python3.14/site-packages/ansible_builder/ee_schema.py
schema_v1 = {
        "version": {
        "ansible_config": {
        "build_arg_defaults": {
        "dependencies": {
        "additional_build_steps": {
schema_v2 = {
        "version": {
        "ansible_config": {
        "build_arg_defaults": {
        "dependencies": {
        "additional_build_steps": {
        "images": {
schema_v3 = {
        "version": {
        "build_arg_defaults": {
        "dependencies": {
        "images": {
        "additional_build_steps": {
        "additional_build_files": {
        "options": {
# 

```

Reverse-engineering `ansible-builder create` might be tricky.

```auto
# cat execution-environment.yml 
---
version: 3

# 
# ansible-builder create
WARNING:root:Using the outdated base image 'quay.io/ansible/ansible-runner:latest' might result in the build failures.
Complete! The build context can be found at: /root/ansible-builder/context
# 
# cat context/Containerfile 
ARG EE_BASE_IMAGE="quay.io/ansible/ansible-runner:latest"
ARG PYCMD="/usr/bin/python3"
ARG PKGMGR_PRESERVE_CACHE=""
...
# 

```