# AWX 24.6.1 – \`make docker-compose-build\` Fails During dnf Install Step

**URL:** <https://forum.ansible.com/t/awx-24-6-1-make-docker-compose-build-fails-during-dnf-install-step/45466>\
**Category:** Get Help\
**Tags:** kubernetes, docker-compose, docker, ubuntu, awx\
**Created:** [March 2, 2026, 2:54pm UTC](https://forum.ansible.com/t/awx-24-6-1-make-docker-compose-build-fails-during-dnf-install-step/45466 "2026-03-02T14:54:46Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![noor](https://avatars.discourse-cdn.com/v4/letter/n/c67d28/32.png) [@noor](https://forum.ansible.com/u/noor)\
**Post date:** [March 2, 2026, 2:54pm UTC](https://forum.ansible.com/t/awx-24-6-1-make-docker-compose-build-fails-during-dnf-install-step/45466/1 "2026-03-02T14:54:46Z")

</div>

Building **AWX** version **24.6.1** from source using Docker fails during the image build phase when running:

```auto
make docker-compose-build

```

The failure occurs during the `dnf install` step inside the container build process.

This issue is reproducible across multiple operating systems.

* * *

## Tested Environments

The issue occurs on:

- Ubuntu 24.04
- Ubuntu 22.04
- Ubuntu 20.04
- CentOS Stream 10

Docker and Docker Compose plugin are installed from official repositories with latest available versions.

Docker is functioning correctly (able to pull other images successfully).

* * *

## Steps to Reproduce

```auto
git clone https://github.com/ansible/awx.git
cd awx
git checkout 24.6.1
make docker-compose-build

```

The build begins normally but fails during package installation inside the container.

* * *

## Error Output

```auto
ERROR: failed to build: failed to solve: process "/bin/sh -c dnf -y update && dnf install -y 'dnf-command(config-manager)' && dnf config-manager --set-enabled crb && dnf -y install iputils gcc gcc-c++ git-core gettext glibc-langpack-en libffi-devel libtool-ltdl-devel make nodejs nss openldap-devel openssl-3.0.7 patch postgresql postgresql-devel python3.11 \"python3.11-devel\" \"python3.11-pip\" \"python3.11-setuptools\" \"python3.11-packaging\" \"python3.11-psycopg2\" swig unzip xmlsec1-devel xmlsec1-openssl-devel" did not complete successfully: exit code: 1

make: *** [Makefile:619: docker-compose-build] Error 1

```

* * *

## Notes

- The failure occurs specifically during the `dnf` execution.
- Since this happens inside the container build stage, host OS differences should not affect the result.
- Network connectivity is confirmed.
- The issue is consistent across all tested distributions.

* * *

## Questions

1. Is `make docker-compose-build` still supported for AWX 24.6.1?
2. Is building via Docker Compose still a supported workflow for 24.x, or is the Kubernetes Operator now the only supported deployment method?
3. Is there updated documentation for building AWX 24.x from source?

* * *

If building from source is no longer the intended workflow for 24.x, clarification on the recommended installation approach would be appreciated.

---

<div class="post-metadata">

**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\
**Post date:** [March 2, 2026, 11:12pm UTC](https://forum.ansible.com/t/awx-24-6-1-make-docker-compose-build-fails-during-dnf-install-step/45466/2 "2026-03-02T23:12:48Z")

</div>

1. The `docker-compose-build` is broken because of how stale it is. In your specific error, the openssl package is pinned to a version that no longer exists in the available repos. If you unpin the version, it will install, but you will encounter more errors as you progress. Theoretically, you should be able to build the image successfully after enough trial and error.
2. The Docker Compose _deployment_ is not and has not been supported since at least AWX 18. Only k8s is supported, but you can deploy via the operator _or_ helm. These methods should still work, but will point to the pre-built images for 24.6.1. If you work your way through building from source, you can point the operator/helm towards a private registry with your builds pushed to it.
3. Any updates to documentation past 24.6.1 will reflect changes in reference to the new modular architecture overhaul, and as such the documentation is also split between the main repo, plugins repo, and any other repo related to the modular architecture. Because docker compose is not supported, there’s not likely to be any related updates.

I had an epiphany to try and use the pre-built image with `docker-compose-sources` followed by `docker-compose-up`, but that led to a whole slew of other issues that prevented it the awx container from starting.

Anyways, I’ve been lucky enough to have access to AAP at work, so I am out of the loop on any legitimate/working ways to deploy AWX currently (whether that’s 24.6.1 or devel). @kurokobo had a very good [AWX on k3s project](https://github.com/kurokobo/awx-on-k3s), but I don’t know if it still works.

---

<div class="post-metadata">

**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\
**Post date:** [March 3, 2026, 11:41am UTC](https://forum.ansible.com/t/awx-24-6-1-make-docker-compose-build-fails-during-dnf-install-step/45466/3 "2026-03-03T11:41:12Z")

</div>

> [@Denney-tech](#):
>
> @kurokobo had a very good [AWX on k3s project](https://github.com/kurokobo/awx-on-k3s), but I don’t know if it still works.

It still works 🙂 - I’m using it in my Homelab:

- [home-ops/ansible/playbooks/playbook-awx-deploy.yml at main · dbrennand/home-ops · GitHub](https://github.com/dbrennand/home-ops/blob/main/ansible/playbooks/playbook-awx-deploy.yml)
- [home-ops/ansible/templates/awx/awx.yaml.j2 at main · dbrennand/home-ops · GitHub](https://github.com/dbrennand/home-ops/blob/main/ansible/templates/awx/awx.yaml.j2)
- [home-ops/ansible/templates/awx/kustomization.yaml.j2 at main · dbrennand/home-ops · GitHub](https://github.com/dbrennand/home-ops/blob/main/ansible/templates/awx/kustomization.yaml.j2)

---

<div class="post-metadata">

**Author:** ![noor](https://avatars.discourse-cdn.com/v4/letter/n/c67d28/32.png) [@noor](https://forum.ansible.com/u/noor)\
**Post date:** [March 11, 2026, 10:11am UTC](https://forum.ansible.com/t/awx-24-6-1-make-docker-compose-build-fails-during-dnf-install-step/45466/4 "2026-03-11T10:11:40Z")

</div>

Hello,

I followed the repository guide to deploy AWX:  
However, the deployment is failing with an `ImagePullBackOff` error.

* * *

### Environment

- OS tested:
  - CentOS Stream 9
  - CentOS Stream 10

- Deployment method: Following the steps exactly from the repository README

* * *

### Events

```auto
Events:
  Type Reason Age From Message
  ---- ------ ---- ---- -------
  Normal BackOff 19m (x5410 over 20h) kubelet Back-off pulling image "gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0"
  Warning FailedCreatePodSandBox 13m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "77c0692e0552b38548c13c9cd66964a4ade5613934cec36a7fc5b15dc648eee5": plugin type="flannel" failed (add): loadFlannelSubnetEnv failed: open /run/flannel/subnet.env: no such file or directory
  Normal SandboxChanged 13m (x2 over 13m) kubelet Pod sandbox changed, it will be killed and re-created.
  Normal Pulled 13m kubelet Container image "quay.io/ansible/awx-operator:2.19.1" already present on machine
  Normal Created 13m kubelet Created container awx-manager
  Normal Started 13m kubelet Started container awx-manager
  Warning Unhealthy 13m (x2 over 13m) kubelet Readiness probe failed: Get "http://10.42.0.7:6789/readyz": dial tcp 10.42.0.7:6789: connect: connection refused
  Warning Failed 13m (x4 over 13m) kubelet Error: ImagePullBackOff
  Normal Pulling 13m (x3 over 13m) kubelet Pulling image "gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0"
  Warning Failed 13m (x3 over 13m) kubelet Failed to pull image "gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0": rpc error: code = NotFound desc = failed to pull and unpack image "gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0": failed to resolve reference "gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0": gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0: not found
  Warning Failed 13m (x3 over 13m) kubelet Error: ErrImagePull
  Normal BackOff 3m53s (x43 over 13m) kubelet Back-off pulling image "gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0"

```

---

<div class="post-metadata">

**Author:** ![noor](https://avatars.discourse-cdn.com/v4/letter/n/c67d28/32.png) [@noor](https://forum.ansible.com/u/noor)\
**Post date:** [March 11, 2026, 11:45am UTC](https://forum.ansible.com/t/awx-24-6-1-make-docker-compose-build-fails-during-dnf-install-step/45466/5 "2026-03-11T11:45:56Z")

</div>

**Update:** `ImagePullBackOff` was due to the deprecated image `gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0`.

**Fix:**

```auto
kubectl -n awx set image deployment/awx-operator-controller-manager \
kube-rbac-proxy=quay.io/brancz/kube-rbac-proxy:v0.15.0
kubectl delete pod -n awx -l control-plane=controller-manager

```

All AWX pods (`web`, `task`, `operator`) are now running and accessible via port-forward:

```auto
kubectl port-forward -n awx svc/awx-service 8080:80 --address 0.0.0.0

```

---

<div class="post-metadata">

**Author:** ![kurokobo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kurokobo/32/182_2.png) [@kurokobo](https://forum.ansible.com/u/kurokobo)\
**Post date:** [March 19, 2026, 3:41pm UTC](https://forum.ansible.com/t/awx-24-6-1-make-docker-compose-build-fails-during-dnf-install-step/45466/6 "2026-03-19T15:41:31Z")

</div>

@Denney-tech @dbrennand @noor  
It’s been quite a while since I last wrote here—hello again!  
Thank you for still introducing and using my repository 🙂

As you’ve mentioned, the images for `kube-rbac-proxy` on `gcr.io` have been deprecated and are no longer available.  
The easiest way to maintain full compatibility is to switch to the image on `quay.io` provided by the original author.

Let me share a proposal for updating the `kustomization.yaml` for the Operator as follows. (I’ve also updated the repository—it’s been a long time since the last one!)

```yaml
...
resources:
  - github.com/ansible/awx-operator/config/default?ref=2.19.1

images:
  - name: quay.io/ansible/awx-operator
    newTag: 2.19.1
  - name: gcr.io/kubebuilder/kube-rbac-proxy 👈👈👈
    newName: quay.io/brancz/kube-rbac-proxy 👈👈👈

```

---

<div class="post-metadata">

**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\
**Post date:** [March 19, 2026, 5:04pm UTC](https://forum.ansible.com/t/awx-24-6-1-make-docker-compose-build-fails-during-dnf-install-step/45466/7 "2026-03-19T17:04:06Z")

</div>

Or you can follow the [PR](https://github.com/ansible-community/awx-operator-helm/pull/81) from the helm charts and use `registry.k8s.io/kubebuilder/kube-rbac-proxy:v0.15.0`

---

<div class="post-metadata">

**Author:** ![kurokobo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kurokobo/32/182_2.png) [@kurokobo](https://forum.ansible.com/u/kurokobo)\
**Post date:** [March 20, 2026, 12:42am UTC](https://forum.ansible.com/t/awx-24-6-1-make-docker-compose-build-fails-during-dnf-install-step/45466/8 "2026-03-20T00:42:03Z")

</div>

@Denney-tech It looks like they ultimately decided to use the image from [quay.io](http://quay.io) for that PR as well 🙂

---

<div class="post-metadata">

**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\
**Post date:** [March 20, 2026, 6:56pm UTC](https://forum.ansible.com/t/awx-24-6-1-make-docker-compose-build-fails-during-dnf-install-step/45466/9 "2026-03-20T18:56:03Z")

</div>

Heh, that’s what I get for not reading the thread or checking the actual file changes!