Had some time to look into it again today. I decide to try it on a new device. So, created a fresh Ubuntu Desktop 22.04 LTS installed both Docker as Podman on it and followed the instructions from this topic as before.
It resulted in the following:
WORKS
sudo docker run -d \
--name="home-assistant" \
-e "TZ=Europe/Amsterdam" \
-e "PUID=1001" \
-e "PGID=8123" \
-e "PACKAGES=iputils" \
-v "/home/hassuser:/config" \
-v "/home/hassuser/docker/run:/etc/services.d/home-assistant/run" \
--net=host \
docker.io/homeassistant/home-assistant:stable
WORKS
sudo podman run -d \
--name="home-assistant" \
-e "TZ=Europe/Amsterdam" \
-e "PUID=1001" \
-e "PGID=8123" \
-e "PACKAGES=iputils" \
-v "/home/hassuser:/config" \
-v "/home/hassuser/docker/run:/etc/services.d/home-assistant/run" \
--net=host \
docker.io/homeassistant/home-assistant:stable
So far, so good. It works in both Docker and Podman. However, when running the following compose file it works with docker compose
but not with podman-compose
version: '3'
services:
hass:
image: docker.io/homeassistant/home-assistant:stable
container_name: home-assistant
restart: unless-stopped
environment:
- TZ=Europe/Amsterdam
- PUID=1001
- PGID=8123
- PACKAGES=iputils
volumes:
- "/home/hassuser/config:/config"
- "/home/hassuser/docker/dockerrun/run:/etc/services.d/home-assistant/run"
security_opt:
- no-new-privileges
ports:
- 8123:8123
So, overall I am happy. I decided to prefer the ‘Podman way’ as it does not run a deamon as Docker does.
Next up: get it to work on my initial setup and (then) move it into the k8 cluster.