Docker-AIO: S3 and SeaweedFS variants, matching DriverVault
Docker-AIO gets the same deployment shapes as DriverVault: plain, SeaweedFS, SeaweedFS split into its roles, and an external S3 endpoint, each as a build-from-source and a prod compose file with an .env example of the same name, plus a README. The from-source SeaweedFS files run the store as side containers; the prod ones build Dockerfile.seaweedfs or Dockerfile.seaweedfs.split, which bake `weed server -s3` or its five separate roles into the image under supervisord. The image is rebuilt around PilotVault's real layout. The old Dockerfile copied "Web App/ui" and "Web App/main.go", which no longer exist, and pinned PocketBase 0.22.21, which cannot run the migrations; it now builds "Web App/web" + "Web App/server" and pins 0.39.11. Unlike DriverVault's nginx front, the Go BFF keeps serving the UI on 8090. Every process runs as an unprivileged user, plugins.json gets an /app/data volume, the container is healthy only when every process answers, and no default superuser credentials are baked in. Verified on Docker from an empty database: plain, both SeaweedFS from-source and both baked prod variants come up healthy, document uploads land in the bucket and download back. The external-S3 files are checked with `docker compose config` only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
5be676fc97
commit
3962530841
20 files changed
+2582
-122
No files matched your search
@@ -0,0 +1,149 @@
|
||||
name: pilotvault-aio
|
||||
|
||||
# Production all-in-one with SeaweedFS split into its roles — and, unlike the
|
||||
# other prod files, built into ONE image here: Dockerfile.seaweedfs.split bakes
|
||||
# master, volume, filer, S3 gateway and the admin UI into the same container as
|
||||
# PocketBase, the API Server and the Web App. One service, one container, four
|
||||
# volumes. Self-contained: one file, no overlays. Everything an operator needs
|
||||
# to set lives in .env.
|
||||
#
|
||||
# 1. cp .env.prod.seaweedfs.split.example .env (then edit it)
|
||||
# 2. docker compose -f docker-compose.prod.seaweedfs.split.yml build
|
||||
# 3. docker compose -f docker-compose.prod.seaweedfs.split.yml up -d
|
||||
#
|
||||
# The build context is the repo root, so this has to run on a host that has the
|
||||
# checkout. To deploy elsewhere, `push` the built image to the registry named in
|
||||
# AIO_IMAGE and `pull` it there — `image:` and `build:` are both set, so the
|
||||
# same file does either.
|
||||
#
|
||||
# What the split buys inside one image: per-role restart under supervisord,
|
||||
# per-role metrics ports, and the SeaweedFS admin UI (weed admin) — a cluster
|
||||
# view, and Object Store → Users, where S3 identities are created and revoked
|
||||
# without touching a file. What it costs against the six-container shape it
|
||||
# replaces: a new SeaweedFS is a rebuild (SEAWEED_VERSION below), not a tag
|
||||
# change, and the roles cannot be spread over hosts. If the object store should
|
||||
# stay outside the app image, use docker-compose.prod.seaweedfs.yml — the S3
|
||||
# behaviour is identical.
|
||||
#
|
||||
# The on-disk layout is the same as every other SeaweedFS shape here: master,
|
||||
# volume and filer share one data mount, exactly as `weed server -dir` lays it
|
||||
# out (master raft state, volume .dat/.idx, the filer's filerldb2/ — no filename
|
||||
# overlap). So a SEAWEED_DATA volume from docker-compose.prod.seaweedfs.yml
|
||||
# mounts here unchanged, and vice versa, with no migration either way.
|
||||
#
|
||||
# Inside the container every SeaweedFS role listens on loopback except the admin
|
||||
# UI. Only the admin UI is published, on loopback by default; PocketBase reaches
|
||||
# the gateway inside. The volume server serves file content by id with no
|
||||
# authentication at all, so it is never reachable from outside; the admin UI
|
||||
# shows what its port would.
|
||||
#
|
||||
# Before turning this on for a stack that already has uploads: PocketBase does
|
||||
# NOT copy existing files into the bucket. See README.md.
|
||||
#
|
||||
# On first boot the S3 gateway's program creates the bucket and seeds
|
||||
# PocketBase's identity into the filer's IAM store, PocketBase upserts the
|
||||
# superuser from POCKETBASE_ADMIN_*, PocketBase runs its bundled migrations
|
||||
# (every collection, the baseline org and the superadmin@pilotvault.local
|
||||
# login), and the API Server points PocketBase's file storage at the bucket.
|
||||
# Every step is idempotent.
|
||||
|
||||
services:
|
||||
pilotvault:
|
||||
build:
|
||||
# Project root (one level up from this compose file), so the Dockerfile
|
||||
# can reach both "API Server/" and "Web App/".
|
||||
context: ..
|
||||
dockerfile: Docker-AIO/Dockerfile.seaweedfs.split
|
||||
args:
|
||||
# Bare names = pass through only when set in the environment, so an
|
||||
# unset PB_VERSION / SEAWEED_VERSION leaves the Dockerfile pin in place
|
||||
# instead of overriding it with an empty string (which for PB_VERSION
|
||||
# would resolve "latest" at build time, and for SEAWEED_VERSION would
|
||||
# not build at all).
|
||||
- PB_VERSION
|
||||
- SEAWEED_VERSION
|
||||
# Tagged for the registry so `docker compose push` lands it where `pull` on
|
||||
# the deploy host expects it.
|
||||
image: "${AIO_IMAGE:-10.2.1.10:5500/admin/pilotvault-aio-seaweedfs-split:latest}"
|
||||
container_name: pilotvault-aio
|
||||
restart: unless-stopped
|
||||
environment:
|
||||
# Superuser (also used by the API Server to authenticate to PocketBase).
|
||||
POCKETBASE_ADMIN_EMAIL: "${POCKETBASE_ADMIN_EMAIL:?set POCKETBASE_ADMIN_EMAIL in .env}"
|
||||
POCKETBASE_ADMIN_PASSWORD: "${POCKETBASE_ADMIN_PASSWORD:?set POCKETBASE_ADMIN_PASSWORD in .env}"
|
||||
# Match CORS to the web origin (only used if a browser calls the API
|
||||
# directly).
|
||||
CORS_ALLOW_ORIGINS: "${CORS_ALLOW_ORIGINS:-http://localhost:8090}"
|
||||
# Probed by the panel status page. The Web App BFF listens on 8090 inside
|
||||
# this container too. Override WEBAPP_URL in .env to make a change from
|
||||
# the panel permanent; the panel alone only holds it for the container's
|
||||
# life.
|
||||
WEBAPP_URL: "${WEBAPP_URL:-http://127.0.0.1:8090}"
|
||||
# --- File storage --------------------------------------------------
|
||||
# The image fixes the rest (PB_S3_ENABLED, the loopback endpoint, path
|
||||
# style, the region): the gateway is inside, at an address that cannot
|
||||
# change. supervisord passes these through to the API Server, which writes
|
||||
# them into PocketBase's settings on every boot, idempotently. Only record
|
||||
# files move — the document store's blobs. The database and PocketBase's
|
||||
# own backups stay on PB_DATA.
|
||||
#
|
||||
# The credentials do double duty: the gateway's program seeds them into
|
||||
# the filer's IAM store as the identity named "pilotvault" (updating it in
|
||||
# place on every boot — that is how a rotated secret lands) *and* they are
|
||||
# what PocketBase authenticates with. No safe defaults; the gateway
|
||||
# refuses to start without them, and with it the whole container.
|
||||
PB_S3_BUCKET: "${PB_S3_BUCKET:-pilotvault}"
|
||||
PB_S3_ACCESS_KEY: "${PB_S3_ACCESS_KEY:?set PB_S3_ACCESS_KEY in .env}"
|
||||
PB_S3_SECRET: "${PB_S3_SECRET:?set PB_S3_SECRET in .env}"
|
||||
# --- SeaweedFS admin UI --------------------------------------------
|
||||
# An unauthenticated panel that can mint credentials for the bucket *is*
|
||||
# the bucket, so the password is required rather than defaulted — weed
|
||||
# leaves auth off entirely when it is empty, and the image refuses to
|
||||
# start the panel at all in that case. Read from WEED_ADMIN_* rather than
|
||||
# a flag, which keeps it off the process command line.
|
||||
WEED_ADMIN_USER: "${SEAWEED_ADMIN_USER:-admin}"
|
||||
WEED_ADMIN_PASSWORD: "${SEAWEED_ADMIN_PASSWORD:?set SEAWEED_ADMIN_PASSWORD in .env}"
|
||||
# Optional view-only login. weed ignores it unless the admin password
|
||||
# above is set, which it is.
|
||||
WEED_ADMIN_READONLY_USER: "${SEAWEED_ADMIN_READONLY_USER:-}"
|
||||
WEED_ADMIN_READONLY_PASSWORD: "${SEAWEED_ADMIN_READONLY_PASSWORD:-}"
|
||||
ports:
|
||||
- "${WEB_PORT:-8090}:8090" # Web App (Go BFF)
|
||||
- "${PB_PORT:-8070}:8070" # PocketBase admin UI / API
|
||||
- "${API_PORT:-8080}:8080" # API Server + panel (root /)
|
||||
# The S3 gateway is not published: PocketBase reaches it inside the
|
||||
# container. The admin UI is, on loopback: storage plumbing, not one of
|
||||
# the app's own panels. On a remote host that means unreachable, so set
|
||||
# SEAWEED_ADMIN_BIND=0.0.0.0 and put it behind a reverse proxy.
|
||||
- "${SEAWEED_ADMIN_BIND:-127.0.0.1}:${SEAWEED_ADMIN_PORT:-23646}:23646"
|
||||
volumes:
|
||||
# Named volumes by default; set any of them to a host path in .env for a
|
||||
# bind mount. PB_DATA: the database and PocketBase's backups. API_DATA:
|
||||
# the API Server's plugins.json (plugin enable-state + config). Back up
|
||||
# PB_DATA and SEAWEED_DATA together — from here on the documents live in
|
||||
# the second, not the first.
|
||||
- "${PB_DATA:-pb_data}:/pb/pb_data"
|
||||
- "${API_DATA:-api_data}:/app/data"
|
||||
- "${SEAWEED_DATA:-seaweed_data}:/seaweed/data"
|
||||
- "${SEAWEED_ADMIN_DATA:-seaweed_admin}:/seaweed/admin"
|
||||
healthcheck:
|
||||
# Every process must answer — the five SeaweedFS roles and the three app
|
||||
# processes. Declared here as well as in the image so the check is
|
||||
# visible, and works against an older pulled image. start_period covers
|
||||
# the SeaweedFS chain plus the first-boot migrations.
|
||||
test: ["CMD-SHELL", "wget -qO- http://127.0.0.1:9333/cluster/status >/dev/null && wget -qO- http://127.0.0.1:8081/healthz >/dev/null && wget -qO- http://127.0.0.1:8888/healthz >/dev/null && wget -qO- http://127.0.0.1:8333/healthz >/dev/null && wget -qO- http://127.0.0.1:23646/health >/dev/null && wget -qO- http://127.0.0.1:8070/api/health >/dev/null && wget -qO- http://127.0.0.1:8080/healthz >/dev/null && wget -qO- http://127.0.0.1:8090/ >/dev/null || exit 1"]
|
||||
interval: 30s
|
||||
timeout: 10s
|
||||
retries: 3
|
||||
start_period: 90s
|
||||
|
||||
volumes:
|
||||
pb_data:
|
||||
api_data:
|
||||
# Master, volume and filer share it — the same layout `weed server -dir`
|
||||
# writes, so this file and docker-compose.prod.seaweedfs.yml can swap places
|
||||
# on it.
|
||||
seaweed_data:
|
||||
# The admin UI's own session key and maintenance-task state. Small, and no
|
||||
# part of the object store.
|
||||
seaweed_admin:
|
||||
Reference in new issue
Block a user