Docker-AIO: one image per database

Dockerfile builds warp-aio on SQLite, Dockerfile.PocketBase builds
warp-aio-pocketbase and Dockerfile.PostgreSQL builds warp-aio-postgresql
with PostgreSQL bundled. The database driver and connection string now
come from the image, so the SQLite and PocketBase images no longer carry
PostgreSQL (103 MB instead of 149 MB). The AIO compose files point at
their own Dockerfile and image, and the entrypoint refuses to start an
embedded PostgreSQL in an image that has none.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
tajniak81andClaude Opus 5.5 committed 2026-10-22 20:22:24 +02:00
1 parent b8d692bac5
commit 89f89b5d36
12 files changed
+275 -59

No files matched your search

+7 -3
View File
@@ -11,9 +11,9 @@
# WARP_AIO_ADMIN=false no admin panel
# WARP_AIO_WEB=false no web client
# WARP_AIO_EMBEDDED_POSTGRES=true PostgreSQL in the container, data in
# $PGDATA (/data/postgres); point
# WARP_DB_CONNECTION_STRING at
# postgres:///warp?host=/run/postgresql&user=warp&sslmode=disable
# $PGDATA (/data/postgres); the default
# in warp-aio-postgresql, the only image
# that has PostgreSQL
set -eu
@@ -53,6 +53,10 @@ shutdown() {
trap 'log "stopping"; shutdown 0' TERM INT
if [ "$WARP_AIO_EMBEDDED_POSTGRES" = true ]; then
if ! command -v postgres >/dev/null; then
log "WARP_AIO_EMBEDDED_POSTGRES=true, but this image has no PostgreSQL; use warp-aio-postgresql"
exit 1
fi
export PGDATA="${PGDATA:-/data/postgres}"
if [ ! -s "$PGDATA/PG_VERSION" ]; then
log "initialising PostgreSQL in $PGDATA"