workshop/awx-debian-ee
Watch
6
0
Fork
You've already forked awx-debian-ee
 0
Code Issues 1 Pull requests Projects Releases Packages 1 Wiki Activity Actions

[work-c3n] ee: drop the receptor binary the image never used #27

Merged
eden merged 1 commit from work-c3n-receptor-binary-is-unpinned-devel-unused into main 2026-11-02 06:01:54 +00:00
Conversation 0 Commits 1 Files changed 2 +4 -4
eden commented 2026-11-02 06:01:42 +00:00
Owner
Copy link

The COPY --from=quay.io/ansible/receptor:devel line was the only thing tying this build to a tag that is republished daily — run 3404 died on sha256:f186e516… because that digest 404s now, and PR #22 re-pinned it, which buys until the next devel push.

It is also unused. AWX container-group jobs run the pod with args = ['ansible-runner', 'worker', '--private-data-dir=/runner'] (awx/main/utils/execution_environments.py), so receptor is never the entry process. The layer is 73.4 MB and the binary in it was 1.6.8+git58f9101 against a controller shipping 1.4.8+d7fe592 — a version skew that only matters in a topology this image is not used in.

Removed: the COPY, the /var/run/receptor directory that existed for the daemon, and the two README claims about it. receptorctl stays in requirements.txt: it is a separate CLI, and it talks to a receptor node over the network rather than to a local binary.

Verification. No container daemon on fractal, so I cannot build here. Grep of the whole build context finds no remaining reference: only receptorctl in requirements.txt and the README sentence explaining the removal. The smoke test in build.yml builds the image and runs tests/playbook.yml through ansible-runner in it, so the main build answers whether the image still works without the layer. I will watch that run and revert if it fails.

Small, contained, reversible: no data, no credentials, no access path. If it turns out some job template does call receptor as an execution node in this EE, the revert is one line.

The `COPY --from=quay.io/ansible/receptor:devel` line was the only thing tying this build to a tag that is republished daily — run 3404 died on `sha256:f186e516…` because that digest 404s now, and PR #22 re-pinned it, which buys until the next devel push. It is also unused. AWX container-group jobs run the pod with `args = ['ansible-runner', 'worker', '--private-data-dir=/runner']` (`awx/main/utils/execution_environments.py`), so receptor is never the entry process. The layer is 73.4 MB and the binary in it was 1.6.8+git58f9101 against a controller shipping 1.4.8+d7fe592 — a version skew that only matters in a topology this image is not used in. Removed: the `COPY`, the `/var/run/receptor` directory that existed for the daemon, and the two README claims about it. `receptorctl` stays in `requirements.txt`: it is a separate CLI, and it talks to a receptor node over the network rather than to a local binary. **Verification.** No container daemon on fractal, so I cannot build here. Grep of the whole build context finds no remaining reference: only `receptorctl` in `requirements.txt` and the README sentence explaining the removal. The smoke test in `build.yml` builds the image and runs `tests/playbook.yml` through `ansible-runner` in it, so the main build answers whether the image still works without the layer. I will watch that run and revert if it fails. Small, contained, reversible: no data, no credentials, no access path. If it turns out some job template does call `receptor` as an execution node in this EE, the revert is one line.
[work-c3n] ee: drop the receptor binary the image never used
All checks were successful
Close bead / close (pull_request) Successful in 4s
Details
1bcfdefc21 
Containerfile copied /usr/bin/receptor from quay.io/ansible/receptor:devel. For
AWX container-group jobs the pod runs `ansible-runner worker
--private-data-dir=/runner`, not receptor, so the copied binary was an unused
~73 MB layer. It was also the only reason the build depended on a tag that is
republished daily: run 3404 died on a digest that 404s, and re-pinning buys until
the next devel push.

Dropping the COPY removes the layer and the dependency. receptorctl stays in
requirements.txt — it is a separate CLI and talks to a receptor node over the
network, it does not need the binary in this image. /var/run/receptor goes with
it: with no daemon there is nothing to put in it.

README updated: the contents list no longer claims receptor + receptorctl, and
the digest-pinning section no longer names a receptor copy that does not exist.
eden merged commit 1e7d5cc23e into main 2026-11-02 06:01:54 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
workshop/awx-debian-ee!27
No description provided.