How to resolve Podman container crash issues for SolidFire Enterprise SDS

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 244

Visibility:: Public

Votes:: 0

Category:: solidfire-enterprise-sds

Specialty:: solidfire

Last Updated:

Applies to

Systems running SolidFire eSDS on RedHat Enterprise Linux 7.6.

Description

This article deals with resolving situations arising from Podman container crashes. There are several situations that can result in a Podman container not being able to start. The signature for all of the situations is the same, an example is below. Most often the container name already in use will be the "config_gen" container. The long number string is the hash of the container overlay and will be the "dangling" overlay seen in the /var/lib/containers/storage/overlay-containers/* directory.

elementctl[24350]: Error: error creating container storage: the container name ... is already in use by "7b41e8138f2505d9f2e4c72347e52d9a5c7a1bcd35f56bf08c31ba47606cfaa9".
 You have to remove that container to be able to reuse that name.: that name is already in use