Podman homeassistant container Exited (100) right after starting

Ask Fedora
, ,
1

My newish Ting Eero router has some nice security features I want to utilize that can only work if I use it for DNS, so I am repurposing a Raspberry Pi 4 I’ve had running as a pihole for years now. I am trying to get Home Assistant to work on it, and I am following this documentation which admittedly may already be outdated:

But when I deploy the container it never seems to start. I do a podman start command, but it never shows up in podman ps. If I do a podman ps --all it shows as status “Up” for several seconds and then it is “Exited (100)”.

[root@rpi4 ~]# podman ps
CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES
[root@rpi4 ~]#
[root@rpi4 ~]# podman ps --all
CONTAINER ID  IMAGE                                          COMMAND     CREATED         STATUS                 PORTS       NAMES
67787ed8bc32  docker.io/homeassistant/home-assistant:stable              22 seconds ago  Up Less than a second              homeassistant
[root@rpi4 ~]#
[root@rpi4 ~]# podman ps --all
CONTAINER ID  IMAGE                                          COMMAND     CREATED         STATUS                 PORTS       NAMES
67787ed8bc32  docker.io/homeassistant/home-assistant:stable              36 seconds ago  Up Less than a second              homeassistant
[root@rpi4 ~]#
[root@rpi4 ~]# podman ps
CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES
[root@rpi4 ~]#
[root@rpi4 ~]# podman ps --all
CONTAINER ID  IMAGE                                          COMMAND     CREATED         STATUS                     PORTS       NAMES
67787ed8bc32  docker.io/homeassistant/home-assistant:stable              46 seconds ago  Exited (100) 1 second ago              homeassistant
[root@rpi4 ~]#
[root@rpi4 ~]# podman start -a 67787ed8bc32
s6-overlay-suexec: fatal: can only run as pid 1
[root@rpi4 ~]#
[root@rpi4 ~]# uname -a; cat /etc/os-release 
Linux rpi4 6.2.14-300.fc38.aarch64 #1 SMP PREEMPT_DYNAMIC Mon May  1 00:58:31 UTC 2023 aarch64 GNU/Linux
NAME="Fedora Linux"
VERSION="38.20230505.0 (IoT Edition)"
ID=fedora
VERSION_ID=38
VERSION_CODENAME=""
PLATFORM_ID="platform:f38"
PRETTY_NAME="Fedora Linux 38.20230505.0 (IoT Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:38"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f38/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=38
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=38
SUPPORT_END=2024-05-14
VARIANT="IoT Edition"
VARIANT_ID=iot
OSTREE_VERSION='38.20230505.0'
[root@rpi4 ~]#

It’s been a while so thanks for any help! I’m trying to research the issue too, so I’ll report back if I can fix it…

2

See if not using --init in the run command helps.

1 Like
3

That was it! Thank you so much, and apologies for the delay… sort of left it for a while and should have checked back.

home_assistant
home_assistant1920×1080 102 KB

Just curious, why did removing the --init help?

4

It looks like there was a breaking change (search for “init”):

1 Like