[annvelents]

Context

getlago/lago#852 (merged after v1.56.0) rebuilds the all-in-one image getlago/lago on the hardened Wolfi bases. getlago/lago-doc#778 documents it on the self-hosted Docker page. The v1.57.0 migration page added in #779 only covered the payment terms backfill.

Description

On guide/migration/migration-to-v1.57.0.mdx:

• The intro lists both changes, and says Docker Compose and Helm installations are not affected by the image change.
• New "The all-in-one image runs as a nonroot user" section: before/after table (user, PostgreSQL 17 → 18, Redis → Valkey, data in /data, PDF in its own container), plus the empty database after the upgrade, LAGO_PDF_URL, and --stop-timeout 40.
• "Why": the root user, the Trivy findings (1 critical, 99 high → 0), and data lost on recreate.
• New "Upgrade the all-in-one image" steps: the one-time chown of an old /data volume, and the commands to start lago-pdf and lago (pinned to v1.57.0).
• The payment terms steps move under "Migrate the customer payment terms". The all-in-one image does not need the customers task: it starts with an empty database, and customers created from v1.57.0 get their payment_term from PaymentTerms::AssignService.

To check before merging

• Merge with docs(self-hosted): document the hardened all-in-one image #778, in the release that ships feat(docker): build the all-in-one image on the Wolfi/apko hardened bases lago#852.
• v1.57.0 is still assumed to be that release.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
lago-docs	🟢 Ready	View Preview	Nov 5, 2026, 2:53 PM

💡 Tip: Enable Automations to automatically generate PRs for you.