XSOAR hosting docker container problem (exit status 125)

[R.Espinel]

Hey,

I have a xsoar instance hosted by PA (saas access) and today none of my containers seems to work. Any script run gives the following message

Error from Scripts is : Script failed to run: "docker images demisto/python3:3.10.13.86272" with error "exit status 125" and output "Error: cannot re-exec process to join the existing user namespace 

Has someone had previously this problem ?.

I don't have access to /reset_containers

Cortex XSOAR 

commands run from engines (owned) work as expected

[Ivetto]

Hello,

First recommendation is to reset the containers and if that doesn't work then restart the docker service. Please follow these troubleshooting steps: 

Scenario 1: Error mounting storage for container

1. For an immediate fix, try to reset Podman's state (for user demisto) by running this on the engine's machine:
   sudo runuser -u demisto podman system reset
   (or just switch to user demisto and run "podman system reset")

2. If the above fails, try to purge Podman's state manually by running:
   sudo rm -rf /var/lib/containers/storage/*
   
   After deleting the above, you may want to rerun "podman system reset" (as demisto) to make sure there are no leftovers.
   
   
3. In case you are still seeing issues - another cleanup command you can try is podman system migrate (run as demisto)
   Some combination of the above commands should eventually get Podman working again. To test it, run (as demisto😞 podman run hello-world
   
   
4. To prevent such issues from happening again, run this command:
   sudo loginctl enable-linger demisto
5. Make sure that Podman's runroot path is mounted on a tmpfs filesystem type. This can be checked with the df command for example, or with: cat /proc/mounts