[openSUSE Leap 15.6] Mariadb Container Issue

[DevDorrejo]

Hello,

Didn't want to create a bug report, because this issue can be layer 8, so I am asking help here.

OS/Packages info:

openSUSE Leap 15.6
Podman v4.9.5
Systemd v254

Hardware info:

CPU: Ryzen 7 3700X
Ram: 128GB
SSD:
1x 1tb ssd: for system
3x 1tb RAID0 BTRFS: for container and services files

• podman info:

host:
arch: amd64
buildahVersion: 1.33.8
cgroupControllers:
- pids
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.1.10-150500.9.9.1.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.1.10, commit: unknown'
cpuUtilization:
idlePercent: 99.17
systemPercent: 0.35
userPercent: 0.48
cpus: 16
databaseBackend: sqlite
distribution:
distribution: opensuse-leap
version: "15.6"
eventLogger: file
freeLocks: 2045
hostname: hostu
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
kernel: 6.4.0-150600.23.14-default
linkmode: dynamic
logDriver: k8s-file
memFree: 116890415104
memTotal: 134975197184
networkBackend: netavark
networkBackendInfo:
backend: netavark
dns:
package: aardvark-dns-1.11.0-150500.3.6.1.x86_64
path: /usr/lib/podman/aardvark-dns
version: aardvark-dns 1.11.0
package: netavark-1.11.0-150500.3.6.1.x86_64
path: /usr/lib/podman/netavark
version: netavark 1.11.0
ociRuntime:
name: runc
package: runc-1.1.12-150000.64.1.x86_64
path: /usr/bin/runc
version: |-
runc version 1.1.12
commit: v1.1.12-0-g51d5e94601ce
spec: 1.0.2-dev
go: go1.21.8
libseccomp: 2.5.3
os: linux
pasta:
executable: ""
package: ""
version: ""
remoteSocket:
exists: false
path: /run/user/1000/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
seccompProfilePath: /etc/containers/seccomp.json
selinuxEnabled: false
serviceIsRemote: false
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.2.2-150600.1.5.x86_64
version: |-
slirp4netns version 1.2.2
commit: 0ee2d87523e906518d34a6b423271e4826f71faf
libslirp: 4.7.0
SLIRP_CONFIG_VERSION_MAX: 5
libseccomp: 2.5.3
swapFree: 134975193088
swapTotal: 134975193088
uptime: 4h 6m 42.00s (Approximately 0.17 days)
variant: ""
plugins:
authorization: null
log:
- k8s-file
- none
- passthrough
- journald
network:
- bridge
- macvlan
- ipvlan
volume:
- local
registries:
search:
- registry.opensuse.org
- registry.suse.com
- docker.io
store:
configFile: /opt/db/aula/.config/containers/storage.conf
containerStore:
number: 1
paused: 0
running: 1
stopped: 0
graphDriverName: overlay
graphOptions: {}
graphRoot: /opt/db/aula/.local/share/containers/storage
graphRootAllocated: 3072628629504
graphRootUsed: 1144035930112
graphStatus:
Backing Filesystem: btrfs
Native Overlay Diff: "true"
Supports d_type: "true"
Supports shifting: "false"
Supports volatile: "true"
Using metacopy: "false"
imageCopyTmpDir: /var/tmp
imageStore:
number: 1
runRoot: /run/user/1000/containers
transientStore: false
volumePath: /opt/db/aula/.local/share/containers/storage/volumes
version:
APIVersion: 4.9.5
Built: 1719835200
BuiltTime: Mon Jul  1 08:00:00 2024
GitCommit: ""
GoVersion: go1.21.11
Os: linux
OsArch: linux/amd64
Version: 4.9.5

I have a rootless container mariadb that freeze podman:

for example:

If I try to restore a db:
podman exec -it db mariadb -pPASSWORD dbs < /opt/backups/db_20240802.sql

It will stay freeze until this message appear: Error: container creation timeout: internal libpod error.

And while it freeze, I can't, in another session, do podman info because it will stay waiting the first command to crash.

I tried restoring the DB inside the container, but it will stuck in some part of the restauration. I tried looking into the processlist, Which will show two users process:

MariaDB [(none)]> show processlist;
+----+------+-----------+------+---------+------+---------------------------------+--------------------------------------------+----------+
| Id | User | Host      | db   | Command | Time | State                           | Info                                       | Progress |
+----+------+-----------+------+---------+------+---------------------------------+--------------------------------------------+----------+
|  4 | root | localhost | aula | Sleep   | 1544 |                                 | NULL                                       |    0.000 |
|  5 | root | localhost | aula | Query   |  311 | Waiting for table metadata lock | DROP TABLE IF EXISTS `mdl_adminpresets_it` |    0.000 |

And it will stay indefinitely there.

So, I want to know: if I am doing something, the container is the one having the issue, the Distro packages or if this can be a podman issue.

If try to stop, restart or kill the container, it will stay in a state of stopping, podman kill won't work.

Thank you for the help, and your patient.

[DevDorrejo]

Another issue, when trying to stop or kill the container won't died.