Merge pull request #502 from sjefferson99/500-raspberry-pi-compatible-docker-images

feat: add support for multi-architecture Docker images with QEMU emul…

Author: sjefferson99

.github/workflows/build-and-push.yml

@@ -48,11 +48,19 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v7
+
+      # Registers QEMU binfmt handlers so Buildx can emulate arm64 on this
+      # amd64 runner to produce multi-architecture images.
+      - name: Set up QEMU
+        uses: docker/setup-qemu-action@v4
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v4
 
       # GITHUB_TOKEN is automatically provided — no PAT or extra secret needed
       - name: Log in to GitHub Container Registry
-        uses: docker/login-action@v3
+        uses: docker/login-action@v4
         with:
           registry: ${{ env.REGISTRY }}
           username: ${{ github.actor }}
@@ -62,7 +70,7 @@ jobs:
 
       - name: Extract metadata for aft (server)
         id: meta-server
-        uses: docker/metadata-action@v5
+        uses: docker/metadata-action@v6
         with:
           images: ${{ env.REGISTRY }}/${{ env.OWNER }}/aft
           tags: |
@@ -78,10 +86,11 @@ jobs:
             type=raw,value=latest,enable=${{ github.ref == 'refs/heads/main' || github.event_name == 'release' }}
 
       - name: Build and push aft (server)
-        uses: docker/build-push-action@v6
+        uses: docker/build-push-action@v7
         with:
           context: .
           file: server/Dockerfile
+          platforms: linux/amd64,linux/arm64
           # On a release event or push to main always push; on manual dispatch respect the input
           push: ${{ github.event_name == 'release' || github.event_name == 'push' || inputs.push_images == 'true' }}
           tags: ${{ steps.meta-server.outputs.tags }}
@@ -91,7 +100,7 @@ jobs:
 
       - name: Extract metadata for aft-web
         id: meta-web
-        uses: docker/metadata-action@v5
+        uses: docker/metadata-action@v6
         with:
           images: ${{ env.REGISTRY }}/${{ env.OWNER }}/aft-web
           tags: |
@@ -102,10 +111,11 @@ jobs:
             type=raw,value=latest,enable=${{ github.ref == 'refs/heads/main' || github.event_name == 'release' }}
 
       - name: Build and push aft-web (nginx + UI)
-        uses: docker/build-push-action@v6
+        uses: docker/build-push-action@v7
         with:
           context: .
           file: server/Dockerfile.nginx
+          platforms: linux/amd64,linux/arm64
           push: ${{ github.event_name == 'release' || github.event_name == 'push' || inputs.push_images == 'true' }}
           tags: ${{ steps.meta-web.outputs.tags }}
           labels: ${{ steps.meta-web.outputs.labels }}

README.md

@@ -66,6 +66,8 @@ Available images:
 - `ghcr.io/sjefferson99/aft:latest` — API server only
 - `ghcr.io/sjefferson99/aft-web:latest` — nginx + UI (proxies to the server)
 
+> **Raspberry Pi / arm64:** Both images are published as multi-architecture manifests covering `linux/amd64` and `linux/arm64`. The same `compose.example.yml` works unmodified on a Raspberry Pi or other arm64 host — `docker compose pull` automatically selects the matching architecture, no extra configuration needed.
+
 ### Server-only deployment
 Remove or comment out the `nginx` service in `compose.example.yml` before renaming it to `compose.yml` to run the API server without the web UI.
 

docs/self-hosted-runner.md

@@ -9,6 +9,9 @@ completely free regardless of how many builds you run.
 - Docker must be installed on the machine that will act as the runner
 - The machine must have internet access to reach GitHub and GHCR
 - Windows, Linux, or macOS are all supported
+- The runner's Docker daemon must allow privileged containers (used by
+  `docker/setup-qemu-action` to register binfmt handlers for cross-building
+  `linux/arm64` images, e.g. for Raspberry Pi)
 
 ---
 
@@ -67,7 +70,12 @@ The workflow (`.github/workflows/build-and-push.yml`) triggers when you
 1. Push your code to `main` as normal
 2. When ready to cut a release, go to GitHub → **Releases** → **Draft a new release**
 3. Create a tag in semver format (e.g. `v1.2.0`) and publish
-4. The runner picks up the job, builds both images, and pushes to GHCR
+4. The runner picks up the job, builds both images for `linux/amd64` and
+   `linux/arm64`, and pushes a single multi-arch manifest per tag to GHCR.
+   `docker pull`/`docker compose pull` automatically grabs the right
+   architecture, so the same images run on a Raspberry Pi without changes.
+   The `arm64` leg is built via QEMU emulation, so builds take noticeably
+   longer than amd64-only builds did.
 
 Images will be available at:
 - `ghcr.io/sjefferson99/aft:latest` (and `ghcr.io/sjefferson99/aft:1.2.0`)

server/Dockerfile

@@ -8,11 +8,7 @@ WORKDIR /app
 # Using retries for better reliability with network issues
 RUN apt-get update || apt-get update || apt-get update
 RUN apt-get install -y --no-install-recommends \
-        gcc \
-        default-libmysqlclient-dev \
         default-mysql-client \
-        pkg-config \
-        build-essential \
         curl && \
     apt-get clean && \
     rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*