Problem with stopping mysql 8

[sglbl]

Issue Description

Describe your issue

Steps to reproduce the issue

Steps to reproduce the issue

1. Create compose.yaml

name: my_service

services:

db:
   image: mysql:8.3
   environment:
     MYSQL_DATABASE: facturation_manager
     MYSQL_ROOT_PASSWORD: ${DOCKER_DB_PASSWORD}
   # labels:
   #   - coolify.type=database
   #   - coolify.service.subType=database
   volumes:
     - db_data:/var/lib/mysql
   ports:
     - "${COOLIFY_DB_PORT:-3309}:3306"

volumes:
 db_data:
     

After I run the compose, when I try to stop the compose every time I get a different error.

(base) sglbl@ddspc:~/deduce/vatsa$ type docker
docker is aliased to `podman'

(base) sglbl@ddspc:~/deduce/vatsa$ which docker-compose 
/usr/local/bin/docker-compose

(base) sglbl@ddspc:~/deduce/vatsa$ systemctl status podman.socket
● podman.socket - Podman API Socket
     Loaded: loaded (/usr/lib/systemd/system/podman.socket; enabled; preset: enabled)
     Active: active (listening) since Wed 2026-03-25 15:26:13 CET; 19min ago
   Triggers: ● podman.service
       Docs: man:podman-system-service(1)
     Listen: /run/podman/podman.sock (Stream)
     CGroup: /system.slice/podman.socket

mar 25 15:26:13 ddspc systemd[1]: Listening on podman.socket - Podman API Socket.
(base) sglbl@ddspc:~/deduce/vatsa$ 

Error response from daemon: container c4b5420b85bed31ad44bf40b1d26f1c619f2336559865dfaa6c12c36fff1cb28 
must be in Created or Stopped state to be started: container state improper

(base) sglbl@ddspc:~/deduce/vatsa$ podman container rm -fa
WARN[0030] StopSignal SIGTERM failed to stop container vatsa-db-1 in 30 seconds, resorting to SIGKILL 
5bf2ad25fb5cc4c8174674011ee9ffbf5d605cd9cc8ca59eb53d6df1157837f4
Error: cannot remove container c4b5420b85bed31ad44bf40b1d26f1c619f2336559865dfaa6c12c36fff1cb28 
as it could not be stopped: given PID did not die within timeout

I added stop_grace_period: 30s but didn't change anything.

Describe the results you received

Only way is to restart. It happened more than once.

Describe the results you expected

To be able to stop mysql container

podman info output

(base) sglbl@ddspc:~$ podman info
host:
  arch: amd64
  buildahVersion: 1.33.7
  cgroupControllers:
  - memory
  - pids
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon_2.1.10+ds1-1build2_amd64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.10, commit: unknown'
  cpuUtilization:
    idlePercent: 93.03
    systemPercent: 1.74
    userPercent: 5.24
  cpus: 12
  databaseBackend: sqlite
  distribution:
    codename: noble
    distribution: zorin
    version: "18"
  eventLogger: journald
  freeLocks: 2046
  hostname: ddspc
  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.17.0-19-generic
  linkmode: dynamic
  logDriver: journald
  memFree: 502341632
  memTotal: 16456794112
  networkBackend: netavark
  networkBackendInfo:
    backend: netavark
    dns:
      package: aardvark-dns_1.4.0-5_amd64
      path: /usr/lib/podman/aardvark-dns
      version: aardvark-dns 1.4.0
    package: netavark_1.4.0-4_amd64
    path: /usr/lib/podman/netavark
    version: netavark 1.4.0
  ociRuntime:
    name: crun
    package: crun_1.14.1-1_amd64
    path: /usr/bin/crun
    version: |-
      crun version 1.14.1
      commit: de537a7965bfbe9992e2cfae0baeb56a08128171
      rundir: /run/user/1000/crun
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +WASM:wasmedge +YAJL
  os: linux
  pasta:
    executable: /usr/bin/pasta
    package: passt_0.0~git20240220.1e6f92b-1_amd64
    version: |
      pasta unknown version
      Copyright Red Hat
      GNU General Public License, version 2 or later
        <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
      This is free software: you are free to change and redistribute it.
      There is NO WARRANTY, to the extent permitted by law.
  remoteSocket:
    exists: true
    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: /usr/share/containers/seccomp.json
    selinuxEnabled: false
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns_1.2.1-1build2_amd64
    version: |-
      slirp4netns version 1.2.1
      commit: 09e31e92fa3d2a1d3ca261adaeb012c8d75a8194
      libslirp: 4.7.0
      SLIRP_CONFIG_VERSION_MAX: 4
      libseccomp: 2.5.5
  swapFree: 17179840512
  swapTotal: 17179865088
  uptime: 0h 25m 42.00s
  variant: ""
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries:
  search:
  - docker.io
store:
  configFile: /home/sglbl/.config/containers/storage.conf
  containerStore:
    number: 1
    paused: 0
    running: 0
    stopped: 1
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /home/sglbl/.local/share/containers/storage
  graphRootAllocated: 501813780480
  graphRootUsed: 468302848000
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Supports shifting: "false"
    Supports volatile: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 19
  runRoot: /run/user/1000/containers
  transientStore: false
  volumePath: /home/sglbl/.local/share/containers/storage/volumes
version:
  APIVersion: 4.9.3
  Built: 0
  BuiltTime: Thu Jan  1 01:00:00 1970
  GitCommit: ""
  GoVersion: go1.22.2
  Os: linux
  OsArch: linux/amd64
  Version: 4.9.3

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

[gen-itals]

I join this issue, as I also experience it, with qbittorent-nox in my case.
I've created issue there qbittorrent/docker-qbittorrent-nox#94 but one of the causes is podman ignoring "stop_grace_period" from container image.

[mheon]

From the image, or from the Compose YAML? Don't think images can set a stop timeout

[gen-itals]

I'm not sure how to answer ... so this is not an expert answer, more of what I know.
I did not user podman-compose. I created the container initially with:
podman run -d --name=qbit2 -it -v qbtconfig:/config -v "/mnt/d/qbt/qb:/downloads:rprivate,rbind" -v "/mnt/d/qbt/qbconf:/config:rprivate,rbind" -e QBT_WEBUI_PORT=8123 -e QBT_TORRENTING_PORT=12345 -e WEBUI_PORT=8080 -e QBT_USERNAME=toor -e QBT_PASSWORD=roottoor -p 8080:8080 -p 12345:12345 -p 12345:12345/udp -p 61684:61684 --dns=1.1.1.1 qbittorrentofficial/qbittorrent-nox:latest
and someone recently hinted to also add "--stop-timeout 1800".

As the maintainer of qbittorrent-nox answered, their stack yaml and compose yaml contains
stop_grace_period: 30m
and from what I understand, other container software (docker desktop, rancher desktop) would respect such entry.

There also seems to be an issue with how Podman mounts Windows shares (as 9p volume). In my case this drive is quite fast nvme ssd, so it is not like "too slow hardware". The workarount was moving config from windows mount to Podman Volume. But this is just going around the issue.

[mheon]

So, compose YAML, then. That is exactly identical to the --stop-timeout option you're using - so if that didn't work, adding an equivalent option to a Compose YAML won't work. I strongly suspect we support that in the Docker API as of now.

[sglbl]

I join this issue, as I also experience it, with qbittorent-nox in my case. I've created issue there qbittorrent/docker-qbittorrent-nox#94 but one of the causes is podman ignoring "stop_grace_period" from container image.

In my case, I also tried to get help from GenAIs (claude opus 4.6, gemini 3.1, chatgpt..) and even they couldn't solve it. One time opus was able to solve the issue by accessing inside the container change ownership etc. But rest of the times all they can say is "it's stuck just restart your pc".

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[sglbl]

Has any one of you tested this?

[sglbl]

Even though I use podman pod rm -f .. I get always get these errors.

I never had these issues with docker and with podman everyday another bug.