[PCA 3.x] Podman Containers Do Not (Re)Start
(Doc ID 2864294.1)
Last updated on JANUARY 06, 2023
Applies to:Private Cloud Appliance X9-2 - Version Not Applicable to Not Applicable [Release NA]
Typically following a Management Node disruption (reboot), the systemd platform podman containers(registry, etcd, vault) may fail to restart, with error that the container already exists:
Aug 9 20:57:39 pcamn01 podman: registry
Aug 9 20:57:39 pcamn01 podman: Error: refusing to remove "registry" as it exists in libpod as container 447ad5e8ee38879158118976dc4b942b16e65cdaba7380403294693b9f9cb08d: container already exists
Aug 9 20:57:39 pcamn01 systemd: Started PCA 3.0 local container registry.
Aug 9 20:57:39 pcamn01 podman: Error: error creating container storage: the container name "registry" is already in use by "447ad5e8ee38879158118976dc4b942b16e65cdaba7380403294693b9f9cb08d". You have to remove that container to be able to reuse that name.: that name is already in use
Aug 9 20:57:39 pcamn01 systemd: registry.service: main process exited, code=exited, status=125/n/a
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document