Docker: S3 and SeaweedFS stacks, matching DriverVault

Docker/ gets the same deployment shapes as DriverVault: plain, SeaweedFS
in the stack, SeaweedFS split into its roles, and an external S3 endpoint,
each as a build-from-source and a registry compose file with an .env
example of the same name, plus a README.

The API Server now reads PB_S3_* on boot and points PocketBase's file
storage at the bucket (only when the settings differ), then asks
PocketBase to test it. It never turns S3 off. Plugin state gets an
api_data volume, since the image could not write plugins.json.

The PocketBase image pinned v0.22.21, which cannot run the v0.23+
migrations or `superuser upsert`; it now pins v0.39.11. Starting from an
empty database also exposed two migration bugs: the seed tried to create
a passwordless account, and the documents collection saved its
self-relation with a blank target. Both are fixed; databases that already
ran them are unaffected.

Verified on Docker: the SeaweedFS and split stacks come up healthy from
an empty database, uploads land in the bucket, and a restart is a no-op.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
tajniak81andClaude Opus 5.5 committed 2026-11-17 17:50:20 +01:00
1 parent bc41d8b128
commit 5be676fc97
26 files changed
+2557 -72

No files matched your search

+18 -8
View File
@@ -10,24 +10,34 @@
# so restarts and upgrades are safe.
#
# BUILD CONTEXT IS THE REPO ROOT (the migrations live under "API Server/"). It is
# built for you by Docker/docker-compose.yml; to build it by hand run from
# E:\VS Code Projects\PilotVault:
# built for you by the Docker/docker-compose*.yml files; to build it by hand run
# from E:\VS Code Projects\PilotVault:
#
# docker build -f Docker/pocketbase/Dockerfile -t pilotvault-pocketbase .
FROM alpine:latest
FROM alpine:3.24
# Pin the version to match the rest of PilotVault; override with --build-arg.
# PB_ARCH is "amd64" (default) or "arm64" (e.g. Apple Silicon).
ARG PB_VERSION=0.22.21
ARG PB_ARCH=amd64
# Pinned so a rebuild months from now produces the same PocketBase. It must be
# v0.23 or newer: the migrations use the v0.23+ JSVM API and the entrypoint uses
# `superuser upsert`. Override to upgrade (--build-arg PB_VERSION=0.40.0); set it
# to empty to resolve the latest release at build time, which needs an
# unauthenticated GitHub API call (rate-limited to 60/hour per IP).
ARG PB_VERSION="0.39.11"
# Provided automatically by BuildKit (amd64 / arm64).
ARG TARGETARCH="amd64"
RUN apk add --no-cache ca-certificates tzdata unzip wget
WORKDIR /pb
RUN set -eux; \
ver="${PB_VERSION}"; \
if [ -z "$ver" ]; then \
ver="$(wget -qO- https://api.github.com/repos/pocketbase/pocketbase/releases/latest \
| grep -o '"tag_name": *"v[^"]*"' | head -1 | sed -E 's/.*"v([^"]+)".*/\1/')"; \
fi; \
echo "Installing PocketBase v${ver} (${TARGETARCH})"; \
wget -q -O /tmp/pb.zip \
"https://github.com/pocketbase/pocketbase/releases/download/v${PB_VERSION}/pocketbase_${PB_VERSION}_linux_${PB_ARCH}.zip"; \
"https://github.com/pocketbase/pocketbase/releases/download/v${ver}/pocketbase_${ver}_linux_${TARGETARCH}.zip"; \
unzip /tmp/pb.zip -d /pb; \
rm /tmp/pb.zip