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.
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.
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, but I don’t know if it still works.
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
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"
@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!)
- I’m using it in my Homelab: