# AAP 2.5-10 install creates Podman volumes then complains they exist

**URL:** <https://forum.ansible.com/t/aap-2-5-10-install-creates-podman-volumes-then-complains-they-exist/40436>\
**Category:** Get Help\
**Tags:** rhel, containerized, aap, awx\
**Created:** [February 21, 2025, 6:04pm UTC](https://forum.ansible.com/t/aap-2-5-10-install-creates-podman-volumes-then-complains-they-exist/40436 "2025-02-21T18:04:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![verxion](https://avatars.discourse-cdn.com/v4/letter/v/a6a055/32.png) [@verxion](https://forum.ansible.com/u/verxion)\
**Post date:** [February 21, 2025, 6:04pm UTC](https://forum.ansible.com/t/aap-2-5-10-install-creates-podman-volumes-then-complains-they-exist/40436/1 "2025-02-21T18:04:29Z")

</div>

Trying to do my first containerized AAP install (using 2.5-10). I’m running almost everything on a single node other than one execution node that is a distinct VM host.

I got a series of errors from “TASK [ansible.containerized\_installer.receptor : Manage the receptor volumes]” indicating that it can’t create volumes. I thought maybe the volumes had been left over from a previous install attempt so I removed the volumes. The subsequent install attempt gave the exact same error.

So this is pretty frustrating. Unless I’m missing something… the ansible install process is:

1. Creating Podman volumes
2. Failing because it can’t create Podman volumes with the very same names it had just created

Here is a sample error. Note that I have four identical errors for “receptor\_run”, “receptor\_runner”, “receptor\_home” and finally “receptor\_data”.

failed: [[aap-en.fqdn.com](http://aap-en.fqdn.com)] (item=receptor\_run) =\> {“ansible\_loop\_var”: “item”, “changed”: false, “item”: “receptor\_run”, “msg”: “Can’t create volume receptor\_run”, “stderr”: “Error: volume with name receptor\_run already exists: volume already exists\n”, “stderr\_lines”: [“Error: volume with name receptor\_run already exists: volume already exists”], “stdout”: “”, “stdout\_lines”: }

Again, just to be explicitly clear, after getting these errors, I:

1. Run “podman volume ls”, validate the volumes the error is talking about all exist (“receptor\_run”, “receptor\_runner”, “receptor\_home” and finally “receptor\_data”.)
2. Run “podman volume rm \<volume\_name\>” for each of the problematic volumes
3. Re-run “podman volume ls” to confirm deletion
4. Re-run the install
5. Get the exact same error complaining that it cannot create the volumes because they already exist

Has anyone else encountered this issue???

-Verxion

---

<div class="post-metadata">

**Author:** ![Austin\_Dyar](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/austin_dyar/32/7170_2.png) [@Austin\_Dyar](https://forum.ansible.com/u/Austin_Dyar)\
**Post date:** [March 10, 2025, 12:24pm UTC](https://forum.ansible.com/t/aap-2-5-10-install-creates-podman-volumes-then-complains-they-exist/40436/2 "2025-03-10T12:24:19Z")

</div>

Are you still having this problem? Or found a solution? I am having the same exact issue.

---

<div class="post-metadata">

**Author:** ![verxion](https://avatars.discourse-cdn.com/v4/letter/v/a6a055/32.png) [@verxion](https://forum.ansible.com/u/verxion)\
**Post date:** [March 10, 2025, 1:49pm UTC](https://forum.ansible.com/t/aap-2-5-10-install-creates-podman-volumes-then-complains-they-exist/40436/3 "2025-03-10T13:49:50Z")

</div>

I had to remove all execution nodes from my inventory file.

-Verxion