Automated Docker Deployments on the Raspberry Pi: Local-First Dev Environments

Operating self-hosted services—such as Home Assistant, Node-RED, and local analytics tracking environments—on a Raspberry Pi often involves manual software updates and ad-hoc configuration adjustments. This traditional approach consumes significant maintenance time and introduces operational risks, including configuration drift, dependency conflicts, and unexpected downtime.

To establish a resilient, deterministic local infrastructure, services must be decoupled from the host operating system. Containerizing the entire smart home and analytics tool landscape via Docker Compose paired with automated deployment pipelines—using local Watchtower setups or structured CI/CD workflows via GitHub Actions—ensures reproducible, zero-downtime edge environments.

1. Containerizing the Edge Landscape with Docker Compose

Docker Compose serves as the declarative baseline for local-first edge architectures. By defining all services, persistent volume mounts, and network bridges within a single version-controlled configuration file, infrastructure state becomes fully reproducible.

# docker-compose.yml: Integrated Smart Home & Local Tracking Stack
services:
  homeassistant:
    container_name: homeassistant
    image: ghcr.io/home-assistant/home-assistant:stable
    volumes:
      - /opt/homeassistant/config:/config
      - /etc/localtime:/etc/localtime:ro
    restart: unless-stopped
    network_mode: host

  nodered:
    container_name: nodered
    image: nodered/node-red:latest
    environment:
      - TZ=Europe/Warsaw
    volumes:
      - /opt/nodered/data:/data
    ports:
      - "1880:1880"
    restart: unless-stopped

  watchtower:
    container_name: watchtower
    image: containrrr/watchtower:latest
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - WATCHTOWER_CLEANUP=true
      - WATCHTOWER_SCHEDULE=0 0 4 * * *
    restart: unless-stopped

A note on the maintenance status: the upstream project containrrr/watchtower was archived on 17 December 2025 and has been read-only since then, so the image receives no further updates or security fixes. The original maintainers have not designated a successor. Development continues in community forks — nickfedor/watchtower (also published as ghcr.io/nicholas-fedor/watchtower) is configuration-compatible and still ships regular releases. The update path for this service should therefore be reviewed before productive use.

In this architecture, persistent data directories reside on reliable external storage (such as a NAS share or SSD), ensuring that container updates never overwrite critical configurations or historical metrics.

2. Automated Maintenance: Watchtower vs. CI/CD Pipelines

Automating deployment and lifecycle management can be achieved through two primary architectural patterns, depending on system complexity and governance requirements:

3. Implementing a GitHub Actions Deployment Pipeline

For custom edge applications or structured infrastructure-as-code (IaC) repositories, deploying via GitHub Actions provides an audit trail of every configuration change. When updates are pushed to the main branch, a workflow connects securely to the Raspberry Pi over SSH to pull changes and reconstruct the stack.

# .github/workflows/deploy-edge.yml
name: Deploy Stack to Raspberry Pi

on:
  push:
    branches:
      - main

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Execute Remote Deployment via SSH
        uses: appleboy/ssh-action@v1.0.0
        with:
          host: ${{ secrets.RPI_HOST }}
          username: ${{ secrets.RPI_USER }}
          key: ${{ secrets.RPI_SSH_KEY }}
          script: |
            cd /opt/edge-stack
            git pull origin main
            docker compose pull
            docker compose up -d --remove-orphans
            docker system prune -f

Summary

Transitioning a Raspberry Pi from a manually configured single-board computer into an automated, containerized edge server minimizes administrative overhead. Whether deploying autonomous updates via Watchtower or deterministic GitOps workflows via GitHub Actions, containerization guarantees a stable, secure, and low-maintenance operational environment for smart home and analytics infrastructures.