On 2/23/24 5:20 AM, Matthias Apitz wrote:
 Hello,
 I'm facing the following small issue while stopping a podman container
 on RedHat 8.9 and SuSE SLES 15SP4. Inside the container runs also a
 SuSE SLES 15SP4:
 $ podman run -d -p 2022:22 -p 28076:8076 -p 23045:3045 7c180cc3c676
 c408e9d468cdebbc11a2d974ccf40e315fa724ada702e713359019a25b2b6882
 ...
 $ podman stop c408e9d468cdebbc11a2d974ccf40e315fa724ada702e713359019a25b2b6882
 WARN[0010] StopSignal SIGQUIT failed to stop container vibrant_bartik in 10 seconds,
resorting to SIGKILL
 c408e9d468cdebbc11a2d974ccf40e315fa724ada702e713359019a25b2b6882
 The Dockerfile which is used to build the container end with:
 $ tail -5 suse/Dockerfile
 EXPOSE 22 8076 3045
 ENTRYPOINT /usr/local/bin/start.sh
 STOPSIGNAL SIGQUIT
 Any ideas what I do wrong?
 	matthias
 
Most likely the program running in start.sh is ignoreing the SIGSTOP signal.