Home Assistant

Home rootful 1 container
homeassistant ghcr.io/home-assistant/home-assistant:stable

Kubernetes YAML

apiVersion: v1
kind: Pod
metadata:
  name: homeassistant
  labels:
    app: homeassistant
spec:
  restartPolicy: Always
  containers:
  - name: homeassistant
    image: ghcr.io/home-assistant/home-assistant:stable
    env:
    - name: TZ
      value: Europe/Vienna
    volumeMounts:
    - name: vol-0
      mountPath: /config
  hostNetwork: true
  volumes:
  - name: vol-0
    persistentVolumeClaim:
      claimName: homeassistant-config

Deployment Guide rootful

Operating System:
!

Prerequisite as root

Install Podman

apt update && apt install -y podman
1

Save the YAML file

sudo mkdir -p /etc/containers/
# Copy the YAML above to:
sudo nano /etc/containers/homeassistant.yaml
2

Test the pod (without systemd)

sudo podman play kube /etc/containers/homeassistant.yaml

# Status:
sudo podman pod ps && sudo podman ps

# Stop:
sudo podman play kube --down /etc/containers/homeassistant.yaml
3

Create Quadlet .kube file (systemd)

Place it at /etc/containers/systemd/homeassistant.kube

sudo mkdir -p /etc/containers/systemd/
cat << 'EOF' | sudo tee /etc/containers/systemd/homeassistant.kube
[Unit]
Description=homeassistant Pod

[Kube]
Yaml=/etc/containers/homeassistant.yaml

[Install]
WantedBy=multi-user.target
EOF
4

Enable systemd service (rootful)

sudo systemctl daemon-reload
sudo systemctl enable --now homeassistant-pod.service
5

Status & Logs

sudo systemctl status homeassistant-pod.service
sudo journalctl -u homeassistant-pod.service -f
sudo podman pod ps
sudo podman ps
Rootful mode:
  • Containers run as root — only use trusted images
  • Ports < 1024 can be bound directly
  • No loginctl enable-linger needed — systemd manages the service
  • Quadlet path: /etc/containers/systemd/ (not ~/.config/)

Ports < 1024 (e.g. 80, 443)

Rootless cannot open privileged ports. Solution:

sysctl net.ipv4.ip_unprivileged_port_start=80

Make persistent in /etc/sysctl.d/99-podman.conf.

Containers communicate via localhost

All containers in the pod share the same network namespace. Always use localhost, not container names.

# Correct (e.g. app → db):
localhost:5432

# Wrong (doesn't work in a pod):
db-container:5432

List open ports

Which ports is the running pod listening on?

podman port homeassistant-pod

Custom DNS for the pod

Set a custom DNS server (e.g. local Pi-hole):

# In YAML under spec.dnsConfig:
spec:
  dnsConfig:
    nameservers:
      - 192.168.1.x

Set volume ownership

Fix permission errors by adjusting UID/GID in the user namespace:

podman unshare chown 1000:1000 /path/to/volume

SELinux volume labels

On SELinux systems (RHEL, Fedora) set the volume suffix:

/host/path:/container/path:Z   # private
/host/path:/container/path:z   # shared

List all volumes

podman volume ls
podman volume inspect <volume-name>

Volume backup

Back up data from a named volume:

podman run --rm \
  -v <volume-name>:/data:ro \
  -v $(pwd):/backup \
  busybox tar czf /backup/backup.tar.gz /data

Cleanup

Remove unused images, containers and volumes:

podman system prune -f        # containers + images
podman image prune -f         # untagged images only
podman volume prune -f        # unused volumes

Automatic image updates (podman-auto-update)

Podman can automatically update images and restart the pod. Enable once:

systemctl --user start podman.socket
systemctl --user daemon-reload
systemctl --user enable --now podman-auto-update.timer
systemctl --user status podman-auto-update.timer

Test without actually updating:

podman auto-update --dry-run

Manual update

Pull a new image version and restart the pod:

podman pull <image>:<tag>
podman play kube --replace \
  ~/.config/containers/homeassistant.yaml

Find outdated images

Check local images against the registry:

podman images --filter dangling=false
podman pull --all-tags <image>

Shell into a running container

podman exec -it homeassistant-<container> /bin/sh
# or bash:
podman exec -it homeassistant-<container> /bin/bash

Follow live logs

# All containers in the pod:
podman pod logs -f homeassistant-pod

# Single container:
podman logs -f homeassistant-<container>

Pod info & resource usage

podman pod inspect homeassistant-pod
podman stats homeassistant-pod

Restart pod without data loss

podman pod restart homeassistant-pod

# or via systemd:
systemctl --user restart homeassistant-pod.service

Customize this stack
Change ports, volumes, environment variables and more in the generator.
Open in Generator