All Instances Silently Fail to Start After Switch to Podman

Technical Support
, ,
1

OS Name/Version: Rocky Linux 9.7

Product Name/Version: AMP 2.7 - 20260308.1

Problem Description:

All instances silently fail to start after running getamp installPodman as root. The following is the full log content of attempting to start an instance. Both docker ps and podman ps show no running containers. ampinstmgr -l shows all instances are up to date, containerized, and not running. This affects both pre-existing instances and newly-created instances.

```
Trying to pull docker.io/cubecoders/ampbase:debian...

Getting image source signatures
Copying blob sha256:c695a66398c499f6d129ab31fd7d88f18dc2b9d196dd6791f462402a7e987282
Copying blob sha256:206356c42440674ecbdf1070cf70ce8ef7885ac2e5c56f1ecf800b758f6b0419
Copying blob sha256:0941cb55672653893af64141e9169c2d5f6ac91bed95910ccc98911405fa4d81
Copying blob sha256:fae913eeead320015638db3f01831e6424a47d2395d09cde9e25c36887de79c8
Copying config sha256:f233dd87e0133ba9c53305e00f7fc46eda1d6976db2c5ddfb369c890f94705e2
Writing manifest to image destination
f233dd87e0133ba9c53305e00f7fc46eda1d6976db2c5ddfb369c890f94705e2

16ca5aa4f19d69bd217811d746ba8941b081ff2bce6286922ddd1d02b7857246
Slow method invocation: StartInstance took 2331ms to complete.
Slow response: ADSModule.StartInstance took 2332ms to complete.
```

Steps to reproduce:

  • Step 1: Perform switch to Podman

Actions taken to resolve so far: Ran kernel upgrades and rebooted. Attempted to use “ampinstmgr –ValidateInstance” command, but all instances throw an “unable to validate” error with the reason of “download cache for 2700 does not exist.” Tried to locate the Container Manager setting described in the patch notes to switch back to Docker, but was unsuccessful.

2

Hold off on Podman for RHEL-based distros including Rocky for the time being - there are additional configuration steps required that will hopefully be addressed in the next AMP update

3

Thanks Greelan, sounds good. Is there a defined process for reverting to docker after the “getamp installPodman” command has already been run?

4

There is a setting in the latest update to select docker as the container manager. Search “container” to find it

5

Ah, perfect. Thank you! I’d looked for that setting before creating the ticket but hadn’t found it. Guess I’m just blind!