Steps to reproduce:
1. Start a container, for testing: podman run --detach --env
MYSQL_ROOT_PASSWORD=p --name mariadb
registry.opensuse.org/opensuse/mariadb:latest
2. wait until initialized
3. Stop the container: podman stop mariadb
4. Check the exit code: podman ls -a; Exited (143)
5. Look at logs: podman logs mariadb
example output:
--------------------------------------------------------------------------------
Session terminated, killing shell...2023-07-08 22:55:08 0 [Note] mysqld
(initiated by: unknown): Normal shutdown
2023-07-08 22:55:08 0 [Note] InnoDB: FTS optimize thread exiting.
2023-07-08 22:55:08 0 [Note] InnoDB: Starting shutdown...
2023-07-08 22:55:08 0 [Note] InnoDB: Dumping buffer pool(s) to
/var/lib/mysql/ib_buffer_pool
2023-07-08 22:55:08 0 [Note] InnoDB: Buffer pool(s) dump completed at 230708
22:55:08
2023-07-08 22:55:08 0 [Note] InnoDB: Removed temporary tablespace data file:
"./ibtmp1"
2023-07-08 22:55:08 0 [Note] InnoDB: Shutdown completed; log sequence number
46456; transaction id 15
2023-07-08 22:55:08 0 [Note] mysqld: Shutdown complete

 ...killed.
--------------------------------------------------------------------------------
This causes trouble when using the image with a systemd service unit since
systemd is going to interpret this as a failed unit.
The official image from Docker Hub does not experience this issue.