Run Metabase in production with Docker

Metabase can be deployed in production with Docker by using a fully pinned official image version, such as metabase/metabase:v0.64.1, rather than moving tags like latest, and by storing its application data in PostgreSQL instead of the container’s default H2 database. The guidance covers Docker Compose configuration with PostgreSQL, Docker secrets for credentials, an encryption key for stored database connection details, restricted HTTP exposure behind a TLS reverse proxy, health checks, JVM memory limits, and time-zone and site URL settings. It recommends daily application-database backups and backups before upgrades, explains migrations and rollback options, and advises using separate application databases for environments and read-only users for analyzed data sources. It also distinguishes liveness, readiness, and full health endpoints to avoid unnecessary restarts during database outages or startup. For managed container services including AWS ECS Fargate, Google Cloud Run, Fly.io, and Render, the same image and environment settings apply, but deployments should retain one continuously running instance for scheduled Metabase tasks, use platform secret management, provide sufficient memory, and avoid running old and new versions concurrently during major upgrades.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.