Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • AAP containerized playbook fails at Create the receptor container

    Posted on

    Haven't seen any posts on this. I'm doing the AAP containerized install on a fresh RHEL9.5. No hardening has been done to the VM. The "ansible.containerized_installer.receptor : Create the receptor container" task fails with the following error

    fatal: [aapvm1.example.com]: FAILED! => {"changed": false, "msg": "Container receptor exited with code 125 when createed", "stderr": "Error: statfs /run/user/1928/podman/podman.sock: no such file or directory\n", "stderr_lines": ["Error: statfs /run/user/1928/podman/podman.sock: no such file or directory"], "stdout": "", "stdout_lines": []}

    Has anyone else seen this?

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2025 Red Hat