Skip to content

podman-restart kills processes after reboot #26008

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ZzenlD opened this issue Apr 29, 2025 · 6 comments
Open

podman-restart kills processes after reboot #26008

ZzenlD opened this issue Apr 29, 2025 · 6 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-info Need info from reporter triaged Issue has been triaged

Comments

@ZzenlD
Copy link

ZzenlD commented Apr 29, 2025 •
edited
Loading

Issue Description

I have provided some podman-compose containers with restart: always and podman-restart should start them automatically after a reboot.

Instead, the following happens with some (but not all) of them:

Apr 29 09:09:06 homebox systemd[1256]: podman-restart.service: Main process exited, code=exited, status=125/n/a
Apr 29 09:10:36 homebox systemd[1256]: podman-restart.service: State 'stop-sigterm' timed out. Killing.
Apr 29 09:10:36 homebox systemd[1256]: podman-restart.service: Killing process 2584 (conmon) with signal SIGKILL.
Apr 29 09:10:36 homebox systemd[1256]: podman-restart.service: Killing process 2701 (conmon) with signal SIGKILL.
Apr 29 09:10:36 homebox systemd[1256]: podman-restart.service: Killing process 2923 (conmon) with signal SIGKILL.
Apr 29 09:10:36 homebox systemd[1256]: podman-restart.service: Killing process 7509 (conmon) with signal SIGKILL.
Apr 29 09:10:36 homebox systemd[1256]: podman-restart.service: Failed with result 'exit-code'.
Apr 29 09:10:36 homebox systemd[1256]: podman-restart.service: Consumed 9.409s CPU time

OS: Suse MicroOS version 20250422
Podman Version:

Client:       Podman Engine
Version:      5.4.2
API Version:  5.4.2
Go Version:   go1.24.2
Built:        Thu Apr  3 17:58:24 2025
OS/Arch:      linux/amd64

podman-restart.service file looks like that:

[Unit]
Description=Podman Start All Containers With Restart Policy Set To Always
Documentation=man:podman-start(1)
StartLimitIntervalSec=0
Wants=network-online.target
After=network-online.target

[Service]
Type=oneshot
RemainAfterExit=true
Environment=LOGGING="--log-level=info"
ExecStart=/usr/bin/podman $LOGGING start --all --filter restart-policy=always
ExecStop=/usr/bin/podman  $LOGGING stop  --all --filter restart-policy=always

[Install]
WantedBy=default.target

I'm not sure if this is related to #12699.

Steps to reproduce the issue

Steps to reproduce the issue

  1. Create a podman-compose file with one service using "restart: always-Policy"
  2. Enable podman-restart service
  3. Reboot System
  4. Watch journalctl -b --grep kill

Describe the results you received

As explained at the beginning, podman-restart kills the processes.

Describe the results you expected

podman-restart starts all services and dont kill them.

podman info output

If you are unable to run podman info for any reason, please provide the podman version, operating system and its version and the architecture you are running.

Podman in a container

No

Privileged Or Rootless

Rootless

Upstream Latest Release

Yes

Additional environment details

Using Suse MicroOS with rootless podman and SELinux

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
@ZzenlD ZzenlD added the kind/bug Categorizes issue or PR as related to a bug. label Apr 29, 2025
@Luap99
Copy link
Member

Luap99 commented Apr 29, 2025

compose is not directly supported by the podman team. Please provide the exact config on how the containers are created and provide the full logs of the podman-restart.service.

If your containers are not reacting to SIGTERM then podman stop will kill it after the stop timeout (10s) so if you have configured a stop timeout higher then the systemd unit timeout then systemd starts killing everything in the unit instead.

@Luap99 Luap99 added the needs-info Need info from reporter label Apr 29, 2025
@github-actions GitHub Actions
Copy link

A reviewer has determined we need more information to understand the reported issue. A comment on what is missing should be provided. Be certain you:

  • provide an exact reproducer where possible
  • verify you have provided all relevant information - minimum is podman info
  • answer any follow up questions

If no response to the needs-info is provided in 30 days, this issue may be closed by our stale bot.

For more information on reporting issues on this repository, consult our issue guide.

@ZzenlD
Copy link
Author

ZzenlD commented Apr 29, 2025 •
edited
Loading

For each service there is a directory under /home/user/<service>, and this directory contains the following compose.yml as an example:

version: "3.9"
services:
  traefik:
    image: docker.io/traefik:v3.0.3
    hostname: traefik
    read_only: true
    security_opt:
      - no-new-privileges
    ports:
      - 80:80
      - 443:443
    volumes:
      - ./traefik/config:/etc/traefik:z,ro
      - ./traefik/var/letsencrypt/acme.json:/letsencrypt/acme.json:z
    labels:
      - io.containers.autoupdate=registry
    healthcheck:
      test: traefik healthcheck --ping
    networks:
      proxy:
        ipv4_address: 10.89.1.2
    restart: always

networks:
  proxy:
    external:
      name: proxy

I start the container with podman-compose up -d.

podman-restart.service-Log contains the following:

Apr 29 11:27:28 homebox systemd[1]: Starting Podman Start All Containers With Restart Policy Set To Always...
Apr 29 11:27:28 homebox podman[1343]: time="2025-04-29T11:27:28+02:00" level=info msg="/usr/bin/podman filtering at log level info"
Apr 29 11:27:28 homebox podman[1343]: time="2025-04-29T11:27:28+02:00" level=info msg="Using sqlite as database backend"
Apr 29 11:27:28 homebox podman[1343]: 2025-04-29 11:27:28.905911881 +0200 CEST m=+0.154990881 system refresh
Apr 29 11:27:28 homebox podman[1343]: time="2025-04-29T11:27:28+02:00" level=info msg="Setting parallel job count to 13"
Apr 29 11:27:28 homebox podman[1343]: time="2025-04-29T11:27:28+02:00" level=info msg="Got Conmon PID as 1389"
Apr 29 11:27:29 homebox podman[1343]: 2025-04-29 11:27:29.02194644 +0200 CEST m=+0.271025435 container init 6c57af47085bad64351893c36ce6354397abddd8bdb320c7b9fa5b1c24dfc15e (image=docker.i>
Apr 29 11:27:29 homebox podman[1343]: 2025-04-29 11:27:29.035723942 +0200 CEST m=+0.284802939 container start 6c57af47085bad64351893c36ce6354397abddd8bdb320c7b9fa5b1c24dfc15e (image=docker>
Apr 29 11:27:29 homebox podman[1343]: 6c57af47085bad64351893c36ce6354397abddd8bdb320c7b9fa5b1c24dfc15e
Apr 29 11:27:29 homebox systemd[1]: Finished Podman Start All Containers With Restart Policy Set To Always.

Edit: The following Systemd output may also help:

Apr 29 11:27:28 homebox (systemd)[1274]: pam_unix(systemd-user:session): session opened for user user(uid=1000) by user(uid=0)
Apr 29 11:27:28 homebox systemd[1274]: Queued start job for default target Main User Target.
Apr 29 11:27:28 homebox systemd[1274]: Created slice User Application Slice.
Apr 29 11:27:28 homebox systemd[1274]: Started Nextcloud cron timer.
Apr 29 11:27:28 homebox systemd[1274]: Started Podman auto-update timer.
Apr 29 11:27:28 homebox systemd[1274]: Started Daily Cleanup of User's Temporary Directories.
Apr 29 11:27:28 homebox systemd[1274]: Reached target Paths.
Apr 29 11:27:28 homebox systemd[1274]: Reached target Timers.
Apr 29 11:27:28 homebox systemd[1274]: Starting D-Bus User Message Bus Socket...
Apr 29 11:27:28 homebox systemd[1274]: Starting Create User Files and Directories...
Apr 29 11:27:28 homebox systemd[1274]: Listening on D-Bus User Message Bus Socket.
Apr 29 11:27:28 homebox systemd[1274]: Reached target Sockets.
Apr 29 11:27:28 homebox systemd[1274]: Finished Create User Files and Directories.
Apr 29 11:27:28 homebox systemd[1274]: Reached target Basic System.
Apr 29 11:27:28 homebox systemd[1274]: Starting Podman Start All Containers With Restart Policy Set To Always...
Apr 29 11:27:28 homebox systemd[1274]: Created slice User Core Session Slice.
Apr 29 11:27:28 homebox systemd[1274]: Starting D-Bus User Message Bus...
Apr 29 11:27:28 homebox systemd[1274]: Started D-Bus User Message Bus.
Apr 29 11:27:28 homebox systemd[1274]: Created slice Slice /user.
Apr 29 11:27:28 homebox systemd[1274]: Created slice cgroup user-libpod_pod_8bd873db4b74b7a62100e85967942ed58e05c4b7e18c9f687adc543d9eb318ba.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_f33bc7a78364655962f161c1581bfc4e0101a5a758c52163a5fcb1df830b6e13.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_ac3b99ea3790a31ab5895dab14b3f153c78695191460cc2e37217048fe9649c0.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_c3e9b1cbe199a0e1e244ed3e16dbc0d04ad085bb9d691ab1fc538713481bd7e3.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_762a404265ce90527c195ac14d16c4a3e2c70abac6ae5c89a5d20674c31127b9.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_bcef9f095d33f73f78d5b7fdeb933d0aa3b7994a7de7f4c3f759b44f87fa832e.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_9ab7b91be38071085e01b0527e136b08f87f34e079d1bcbd4789bdbba963ee7f.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_6211ef8a1c85162008a3d3eebcffdaa09e491d80e0b8cf4fa04b72237cb984c5.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_9fd3092c60bc149446097a2051c721a93298419842dd724838ce178a99d76621.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_86aedf071527f09ee43a317cb1a3442e382eff1d93480de907da33b51e6770ee.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_cf446d08026b923febde16ee244453b3a4401347f0e8747abb01f50d2cd5d26d.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_05f2c9cfdeeee7fb6c2716927a46e4b7c0446af29c1a4f72b6f1625db188d618.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_5c7bf94cd442697c57b207f4161ef786253da41e0f7fe34aa747ca9765f0f7d2.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_a2b14266d5174e4197382cd83f1ca727634658733afca89ee812105de64c15e8.slice.
Apr 29 11:27:29 homebox systemd[1274]: Created slice cgroup user-libpod_pod_e2e517848758a988ec78859c447fb9ba9cb89d7bc8b6a8fe74483c2ebd243a1e.slice.
Apr 29 11:27:29 homebox systemd[1274]: Started rootless-netns-58a200f1.scope.
Apr 29 11:27:29 homebox systemd[1274]: Started [systemd-run] /usr/libexec/podman/aardvark-dns --config /run/user/1000/containers/networks/aardvark-dns -p 53 run.
Apr 29 11:27:29 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:37 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 5f1ce4d351510427df4982989a1b179a158cc0d4ea2c90ad1d48036ac3326b31.
Apr 29 11:27:37 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:38 homebox systemd[1274]: 5f1ce4d351510427df4982989a1b179a158cc0d4ea2c90ad1d48036ac3326b31-565659781eb970f.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:38 homebox systemd[1274]: 5f1ce4d351510427df4982989a1b179a158cc0d4ea2c90ad1d48036ac3326b31-565659781eb970f.service: Failed with result 'exit-code'.
Apr 29 11:27:38 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 792de46bd0a123641e531ac765c8dfe50413f2c675e32bee153ea65970f4b947.
Apr 29 11:27:38 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:38 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 79be158bfef4bbdb486e8a0450e68d995e2538fe338e53922033cf919bb8b343.
Apr 29 11:27:38 homebox systemd[1274]: 792de46bd0a123641e531ac765c8dfe50413f2c675e32bee153ea65970f4b947-42eaa14ee092ee2.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:38 homebox systemd[1274]: 792de46bd0a123641e531ac765c8dfe50413f2c675e32bee153ea65970f4b947-42eaa14ee092ee2.service: Failed with result 'exit-code'.
Apr 29 11:27:38 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:38 homebox systemd[1274]: 79be158bfef4bbdb486e8a0450e68d995e2538fe338e53922033cf919bb8b343-1c42fbe1930e6e70.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:38 homebox systemd[1274]: 79be158bfef4bbdb486e8a0450e68d995e2538fe338e53922033cf919bb8b343-1c42fbe1930e6e70.service: Failed with result 'exit-code'.
Apr 29 11:27:38 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run f9a707dd77ccff4fc156a8485de5cf3f08b810cf91153b7d44a097a9619b7f37.
Apr 29 11:27:39 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:39 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 9705bfb08e9a6c729e8086a73ccf6745c5fcd857ad2082d9f13d7faa8195f39b.
Apr 29 11:27:39 homebox systemd[1274]: f9a707dd77ccff4fc156a8485de5cf3f08b810cf91153b7d44a097a9619b7f37-53eef7afa7b8423e.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:39 homebox systemd[1274]: f9a707dd77ccff4fc156a8485de5cf3f08b810cf91153b7d44a097a9619b7f37-53eef7afa7b8423e.service: Failed with result 'exit-code'.
Apr 29 11:27:39 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:39 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 7f40773b2c07abc1107be4d6d5256261c02f02bc6941a06100b12e20976430de.
Apr 29 11:27:39 homebox systemd[1274]: 9705bfb08e9a6c729e8086a73ccf6745c5fcd857ad2082d9f13d7faa8195f39b-38e5400e5fe6a68a.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:39 homebox systemd[1274]: 9705bfb08e9a6c729e8086a73ccf6745c5fcd857ad2082d9f13d7faa8195f39b-38e5400e5fe6a68a.service: Failed with result 'exit-code'.
Apr 29 11:27:39 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:39 homebox systemd[1274]: 7f40773b2c07abc1107be4d6d5256261c02f02bc6941a06100b12e20976430de-2c310da8bf2e1b34.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:39 homebox systemd[1274]: 7f40773b2c07abc1107be4d6d5256261c02f02bc6941a06100b12e20976430de-2c310da8bf2e1b34.service: Failed with result 'exit-code'.
Apr 29 11:27:40 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run ed64b4855f50dda549cb5b9220b42b0f0314454599607989654dd9bad052a390.
Apr 29 11:27:40 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:40 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run fbd55cb4aceba4c6699e04b9abc6642c1a20e16ad062d0ba5926de3d4d53c601.
Apr 29 11:27:40 homebox systemd[1274]: ed64b4855f50dda549cb5b9220b42b0f0314454599607989654dd9bad052a390-64d4dc846c49dcd2.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:40 homebox systemd[1274]: ed64b4855f50dda549cb5b9220b42b0f0314454599607989654dd9bad052a390-64d4dc846c49dcd2.service: Failed with result 'exit-code'.
Apr 29 11:27:40 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:40 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run aa337d90972b60ffded5210127d5cf6579497ef8f4959de6521aa35eaa4b9c31.
Apr 29 11:27:40 homebox systemd[1274]: fbd55cb4aceba4c6699e04b9abc6642c1a20e16ad062d0ba5926de3d4d53c601-4054a233f66eadce.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:40 homebox systemd[1274]: fbd55cb4aceba4c6699e04b9abc6642c1a20e16ad062d0ba5926de3d4d53c601-4054a233f66eadce.service: Failed with result 'exit-code'.
Apr 29 11:27:42 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:42 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 1919dab18c63cd2fcc1aa76cac785f59055acb999e80331b1874d39ce9ff127c.
Apr 29 11:27:42 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:43 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run de4eb3417521946213c5fff9c7722527bea8d7e42ffb168b44cdf8aa053cb13f.
Apr 29 11:27:43 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:43 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 1c9704d03b7b3fa5cac53609c58bbb4b7c8f7d610dc41f073cf15f56bd50e291.
Apr 29 11:27:43 homebox systemd[1274]: de4eb3417521946213c5fff9c7722527bea8d7e42ffb168b44cdf8aa053cb13f-468badd946776ed6.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:43 homebox systemd[1274]: de4eb3417521946213c5fff9c7722527bea8d7e42ffb168b44cdf8aa053cb13f-468badd946776ed6.service: Failed with result 'exit-code'.
Apr 29 11:27:43 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:43 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 071a534b97df980c8c12889ab60c3fd9faab98659ce3c20202f009907e24507a.
Apr 29 11:27:43 homebox systemd[1274]: 1919dab18c63cd2fcc1aa76cac785f59055acb999e80331b1874d39ce9ff127c-481e907019914813.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:43 homebox systemd[1274]: 1919dab18c63cd2fcc1aa76cac785f59055acb999e80331b1874d39ce9ff127c-481e907019914813.service: Failed with result 'exit-code'.
Apr 29 11:27:43 homebox systemd[1274]: 1c9704d03b7b3fa5cac53609c58bbb4b7c8f7d610dc41f073cf15f56bd50e291-35ebccf43788b9d8.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:43 homebox systemd[1274]: 1c9704d03b7b3fa5cac53609c58bbb4b7c8f7d610dc41f073cf15f56bd50e291-35ebccf43788b9d8.service: Failed with result 'exit-code'.
Apr 29 11:27:44 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:44 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run d02254050f378f7961f3b20d17cff993b988425256c40520c324e76ee6998168.
Apr 29 11:27:44 homebox systemd[1274]: 071a534b97df980c8c12889ab60c3fd9faab98659ce3c20202f009907e24507a-201f50528789a51.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:44 homebox systemd[1274]: 071a534b97df980c8c12889ab60c3fd9faab98659ce3c20202f009907e24507a-201f50528789a51.service: Failed with result 'exit-code'.
Apr 29 11:27:44 homebox systemd[1274]: d02254050f378f7961f3b20d17cff993b988425256c40520c324e76ee6998168-633000534aa454fa.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:44 homebox systemd[1274]: d02254050f378f7961f3b20d17cff993b988425256c40520c324e76ee6998168-633000534aa454fa.service: Failed with result 'exit-code'.
Apr 29 11:27:45 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:45 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run bb253542037ed2261436efb6f6729c3aee3d26f49c7309165f5f9b21b0fda4ef.
Apr 29 11:27:45 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:45 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 299db051d835f020a3f72652ee90a554f440a916c5913d8336fbf41d714eccac.
Apr 29 11:27:46 homebox systemd[1274]: Started libcontainer container cba5e279ab7d2dafbf2650f87754d6134cac68afa40593ad9fc20896364c3bef.
Apr 29 11:27:46 homebox systemd[1274]: 299db051d835f020a3f72652ee90a554f440a916c5913d8336fbf41d714eccac-3b159c1ff0ffa9bb.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:46 homebox systemd[1274]: 299db051d835f020a3f72652ee90a554f440a916c5913d8336fbf41d714eccac-3b159c1ff0ffa9bb.service: Failed with result 'exit-code'.
Apr 29 11:27:46 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run cba5e279ab7d2dafbf2650f87754d6134cac68afa40593ad9fc20896364c3bef.
Apr 29 11:27:46 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:27:47 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:27:47 homebox systemd[1274]: Started podman-pause-f4b01f5a.scope.
Apr 29 11:27:47 homebox systemd[1274]: podman-restart.service: Main process exited, code=exited, status=125/n/a
Apr 29 11:27:47 homebox systemd[1274]: 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef-6337bcf23d7274a3.service: Main process exited, code=exited, status=125/n/a
Apr 29 11:27:47 homebox systemd[1274]: 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef-6337bcf23d7274a3.service: Failed with result 'exit-code'.
Apr 29 11:27:47 homebox systemd[1274]: libpod-7f40773b2c07abc1107be4d6d5256261c02f02bc6941a06100b12e20976430de.scope: Consumed 3.790s CPU time.
Apr 29 11:27:47 homebox systemd[1274]: libpod-79be158bfef4bbdb486e8a0450e68d995e2538fe338e53922033cf919bb8b343.scope: Consumed 1.362s CPU time.
Apr 29 11:27:47 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run bb253542037ed2261436efb6f6729c3aee3d26f49c7309165f5f9b21b0fda4ef.
Apr 29 11:27:48 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 7f40773b2c07abc1107be4d6d5256261c02f02bc6941a06100b12e20976430de.
Apr 29 11:27:48 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:27:48 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run aa337d90972b60ffded5210127d5cf6579497ef8f4959de6521aa35eaa4b9c31.
Apr 29 11:27:48 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run f9a707dd77ccff4fc156a8485de5cf3f08b810cf91153b7d44a097a9619b7f37.
Apr 29 11:27:48 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run cba5e279ab7d2dafbf2650f87754d6134cac68afa40593ad9fc20896364c3bef.
Apr 29 11:27:48 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 79be158bfef4bbdb486e8a0450e68d995e2538fe338e53922033cf919bb8b343.
Apr 29 11:27:48 homebox systemd[1274]: libpod-5f1ce4d351510427df4982989a1b179a158cc0d4ea2c90ad1d48036ac3326b31.scope: Consumed 14.168s CPU time.
Apr 29 11:27:48 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 5f1ce4d351510427df4982989a1b179a158cc0d4ea2c90ad1d48036ac3326b31.
Apr 29 11:27:48 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:48 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:27:48 homebox systemd[1274]: libpod-fbd55cb4aceba4c6699e04b9abc6642c1a20e16ad062d0ba5926de3d4d53c601.scope: Consumed 3.736s CPU time.
Apr 29 11:27:48 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run aa337d90972b60ffded5210127d5cf6579497ef8f4959de6521aa35eaa4b9c31.
Apr 29 11:27:48 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:48 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run f9a707dd77ccff4fc156a8485de5cf3f08b810cf91153b7d44a097a9619b7f37.
Apr 29 11:27:48 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:48 homebox systemd[1274]: Started libcontainer container cba5e279ab7d2dafbf2650f87754d6134cac68afa40593ad9fc20896364c3bef.
Apr 29 11:27:48 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:48 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:27:48 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run fbd55cb4aceba4c6699e04b9abc6642c1a20e16ad062d0ba5926de3d4d53c601.
Apr 29 11:27:48 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 79be158bfef4bbdb486e8a0450e68d995e2538fe338e53922033cf919bb8b343.
Apr 29 11:27:49 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run cba5e279ab7d2dafbf2650f87754d6134cac68afa40593ad9fc20896364c3bef.
Apr 29 11:27:49 homebox systemd[1274]: libpod-ed64b4855f50dda549cb5b9220b42b0f0314454599607989654dd9bad052a390.scope: Consumed 2.409s CPU time.
Apr 29 11:27:49 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:49 homebox systemd[1274]: libpod-de4eb3417521946213c5fff9c7722527bea8d7e42ffb168b44cdf8aa053cb13f.scope: Consumed 2.451s CPU time.
Apr 29 11:27:49 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 7f40773b2c07abc1107be4d6d5256261c02f02bc6941a06100b12e20976430de.
Apr 29 11:27:49 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:49 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:49 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run bb253542037ed2261436efb6f6729c3aee3d26f49c7309165f5f9b21b0fda4ef.
Apr 29 11:27:49 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run ed64b4855f50dda549cb5b9220b42b0f0314454599607989654dd9bad052a390.
Apr 29 11:27:49 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run de4eb3417521946213c5fff9c7722527bea8d7e42ffb168b44cdf8aa053cb13f.
Apr 29 11:27:49 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run fbd55cb4aceba4c6699e04b9abc6642c1a20e16ad062d0ba5926de3d4d53c601.
Apr 29 11:27:49 homebox systemd[1274]: 79be158bfef4bbdb486e8a0450e68d995e2538fe338e53922033cf919bb8b343-5ded26f5d1a1a6d6.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:49 homebox systemd[1274]: 79be158bfef4bbdb486e8a0450e68d995e2538fe338e53922033cf919bb8b343-5ded26f5d1a1a6d6.service: Failed with result 'exit-code'.
Apr 29 11:27:49 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:49 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:49 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run d02254050f378f7961f3b20d17cff993b988425256c40520c324e76ee6998168.
Apr 29 11:27:50 homebox systemd[1274]: 7f40773b2c07abc1107be4d6d5256261c02f02bc6941a06100b12e20976430de-4b4f59ae81eb2061.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:50 homebox systemd[1274]: 7f40773b2c07abc1107be4d6d5256261c02f02bc6941a06100b12e20976430de-4b4f59ae81eb2061.service: Failed with result 'exit-code'.
Apr 29 11:27:50 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run ed64b4855f50dda549cb5b9220b42b0f0314454599607989654dd9bad052a390.
Apr 29 11:27:50 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run de4eb3417521946213c5fff9c7722527bea8d7e42ffb168b44cdf8aa053cb13f.
Apr 29 11:27:50 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:50 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run d02254050f378f7961f3b20d17cff993b988425256c40520c324e76ee6998168.
Apr 29 11:27:50 homebox systemd[1274]: de4eb3417521946213c5fff9c7722527bea8d7e42ffb168b44cdf8aa053cb13f-7fc9c64485b7d55d.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:50 homebox systemd[1274]: de4eb3417521946213c5fff9c7722527bea8d7e42ffb168b44cdf8aa053cb13f-7fc9c64485b7d55d.service: Failed with result 'exit-code'.
Apr 29 11:27:50 homebox systemd[1274]: ed64b4855f50dda549cb5b9220b42b0f0314454599607989654dd9bad052a390-4ec2afa11d6c6e3f.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:50 homebox systemd[1274]: ed64b4855f50dda549cb5b9220b42b0f0314454599607989654dd9bad052a390-4ec2afa11d6c6e3f.service: Failed with result 'exit-code'.
Apr 29 11:27:51 homebox systemd[1274]: fbd55cb4aceba4c6699e04b9abc6642c1a20e16ad062d0ba5926de3d4d53c601-94f9fc44b198d1b.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:51 homebox systemd[1274]: fbd55cb4aceba4c6699e04b9abc6642c1a20e16ad062d0ba5926de3d4d53c601-94f9fc44b198d1b.service: Failed with result 'exit-code'.
Apr 29 11:27:52 homebox systemd[1274]: libpod-792de46bd0a123641e531ac765c8dfe50413f2c675e32bee153ea65970f4b947.scope: Consumed 7.371s CPU time.
Apr 29 11:27:52 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 792de46bd0a123641e531ac765c8dfe50413f2c675e32bee153ea65970f4b947.
Apr 29 11:27:52 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:53 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 792de46bd0a123641e531ac765c8dfe50413f2c675e32bee153ea65970f4b947.
Apr 29 11:27:53 homebox systemd[1274]: 792de46bd0a123641e531ac765c8dfe50413f2c675e32bee153ea65970f4b947-444c13ef7a9f14f9.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:53 homebox systemd[1274]: 792de46bd0a123641e531ac765c8dfe50413f2c675e32bee153ea65970f4b947-444c13ef7a9f14f9.service: Failed with result 'exit-code'.
Apr 29 11:27:54 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 5f1ce4d351510427df4982989a1b179a158cc0d4ea2c90ad1d48036ac3326b31.
Apr 29 11:27:55 homebox systemd[1274]: 5f1ce4d351510427df4982989a1b179a158cc0d4ea2c90ad1d48036ac3326b31-4c2fe622bb26a3db.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:55 homebox systemd[1274]: 5f1ce4d351510427df4982989a1b179a158cc0d4ea2c90ad1d48036ac3326b31-4c2fe622bb26a3db.service: Failed with result 'exit-code'.
Apr 29 11:27:56 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:27:56 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:27:56 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:27:57 homebox systemd[1274]: libpod-9705bfb08e9a6c729e8086a73ccf6745c5fcd857ad2082d9f13d7faa8195f39b.scope: Consumed 1.796s CPU time.
Apr 29 11:27:57 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 9705bfb08e9a6c729e8086a73ccf6745c5fcd857ad2082d9f13d7faa8195f39b.
Apr 29 11:27:58 homebox systemd[1274]: Started libcrun container.
Apr 29 11:27:58 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 9705bfb08e9a6c729e8086a73ccf6745c5fcd857ad2082d9f13d7faa8195f39b.
Apr 29 11:27:58 homebox systemd[1274]: 9705bfb08e9a6c729e8086a73ccf6745c5fcd857ad2082d9f13d7faa8195f39b-6ddce4acafaa6e61.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:27:58 homebox systemd[1274]: 9705bfb08e9a6c729e8086a73ccf6745c5fcd857ad2082d9f13d7faa8195f39b-6ddce4acafaa6e61.service: Failed with result 'exit-code'.
Apr 29 11:28:02 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:03 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:03 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:10 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:10 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:11 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:14 homebox systemd[1274]: 1919dab18c63cd2fcc1aa76cac785f59055acb999e80331b1874d39ce9ff127c-481e907019914813.service: Main process exited, code=exited, status=125/n/a
Apr 29 11:28:14 homebox systemd[1274]: 1919dab18c63cd2fcc1aa76cac785f59055acb999e80331b1874d39ce9ff127c-481e907019914813.service: Failed with result 'exit-code'.
Apr 29 11:28:18 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:18 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:18 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:21 homebox systemd[1274]: 7f40773b2c07abc1107be4d6d5256261c02f02bc6941a06100b12e20976430de-4b4f59ae81eb2061.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:28:21 homebox systemd[1274]: 7f40773b2c07abc1107be4d6d5256261c02f02bc6941a06100b12e20976430de-4b4f59ae81eb2061.service: Failed with result 'exit-code'.
Apr 29 11:28:24 homebox systemd[1274]: 792de46bd0a123641e531ac765c8dfe50413f2c675e32bee153ea65970f4b947-444c13ef7a9f14f9.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:28:24 homebox systemd[1274]: 792de46bd0a123641e531ac765c8dfe50413f2c675e32bee153ea65970f4b947-444c13ef7a9f14f9.service: Failed with result 'exit-code'.
Apr 29 11:28:25 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:25 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:25 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:32 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:32 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:32 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:39 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:39 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:39 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:44 homebox systemd[1274]: 1919dab18c63cd2fcc1aa76cac785f59055acb999e80331b1874d39ce9ff127c-481e907019914813.service: Main process exited, code=exited, status=125/n/a
Apr 29 11:28:44 homebox systemd[1274]: 1919dab18c63cd2fcc1aa76cac785f59055acb999e80331b1874d39ce9ff127c-481e907019914813.service: Failed with result 'exit-code'.
Apr 29 11:28:46 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:47 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:47 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:53 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:54 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:54 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:28:59 homebox systemd[1274]: 792de46bd0a123641e531ac765c8dfe50413f2c675e32bee153ea65970f4b947-444c13ef7a9f14f9.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 11:28:59 homebox systemd[1274]: 792de46bd0a123641e531ac765c8dfe50413f2c675e32bee153ea65970f4b947-444c13ef7a9f14f9.service: Failed with result 'exit-code'.
Apr 29 11:29:00 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:29:00 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:29:01 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:29:07 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:29:08 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:29:08 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:29:14 homebox systemd[1274]: 1919dab18c63cd2fcc1aa76cac785f59055acb999e80331b1874d39ce9ff127c-481e907019914813.service: Main process exited, code=exited, status=125/n/a
Apr 29 11:29:14 homebox systemd[1274]: 1919dab18c63cd2fcc1aa76cac785f59055acb999e80331b1874d39ce9ff127c-481e907019914813.service: Failed with result 'exit-code'.
Apr 29 11:29:15 homebox systemd[1274]: Stopped [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:29:15 homebox systemd[1274]: Started libcontainer container 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:29:15 homebox systemd[1274]: Started [systemd-run] /usr/bin/podman healthcheck run 22fff082bbaa5fc5fe75234e778fa8bd376a5b4f635f5cc142ceba255e36d3ef.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: State 'stop-sigterm' timed out. Killing.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 2611 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 2716 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 2936 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 3441 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 3508 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 3520 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 3545 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 3562 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 3720 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 3738 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 3771 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 3845 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 3852 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 3918 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 4279 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 4291 (rootlessport) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 4298 (exe) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 4923 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Killing process 7330 (conmon) with signal SIGKILL.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Failed with result 'exit-code'.
Apr 29 11:29:17 homebox systemd[1274]: Failed to start Podman Start All Containers With Restart Policy Set To Always.
Apr 29 11:29:17 homebox systemd[1274]: podman-restart.service: Consumed 8.756s CPU time.
Apr 29 11:29:17 homebox systemd[1274]: Reached target Main User Target.
Apr 29 11:29:17 homebox systemd[1274]: Startup finished in 1min 49.424s.

@Luap99
Copy link
Member

Luap99 commented Apr 29, 2025

Thanks, I don't see the podman stop command ever being called by systemd, I think because there is nor proper mainpid setup systemd doesn't know which process to track exactly and it seems whatever process it used is exiting > 0 ("podman-restart.service: Main process exited, code=exited, status=125/n/a") which means ExecStop= is never called.

If you modify the the systemd unit to use ExecStopPost= instead of ExecStop= does it work correctly?

@Luap99 Luap99 added the triaged Issue has been triaged label Apr 29, 2025
@ZzenlD
Copy link
Author

ZzenlD commented Apr 29, 2025

Unfortunately, Suse MicroOS is immutable, so /etc cannot be customized.

@Luap99
Copy link
Member

Luap99 commented Apr 29, 2025

systemd supports overwrites in /run as well, you can write the whole unit to /run/systemd/system/ for the system session (root) and /run/systemd/user/ for the user session (rootless) as well.
https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html#System%20Unit%20Search%20Path

Also people still need customize config files so I assume they still must have a way to edit /etc config files somehow?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-info Need info from reporter triaged Issue has been triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Luap99 @ZzenlD