>liquibase

liquibase

Provides a database schema change management and version control tool designed to help teams safely evolve and deploy database changes across environments.

flyway

postgres

mysql

maven

What is liquibase image?

The liquibase image runs Liquibase, an open-source database migration and change management tool. It enables developers and DevOps teams to track, version, and automate database schema changes alongside application code. Liquibase supports rollback operations, diff generation, and deployment automation across multiple database systems including PostgreSQL, MySQL, Oracle, SQL Server, and others.

The image is especially valuable in CI/CD pipelines where database changes need to be applied consistently between development, staging, and production environments. Liquibase uses changelog files written in XML, YAML, JSON, or SQL to define schema changes declaratively, providing traceability and repeatability for database evolution.

In containerized infrastructure, the liquibase image helps unify application and database delivery processes, ensuring schema migrations can be automated, reviewed, and version-controlled like any other code artifact.

How to use this image

The liquibase image can be used to run database updates, generate change logs, or test schema differences between environments. It can connect to any supported database via JDBC.

Run a migration from a changelog file:

docker run --rm \
  -v $(pwd):/liquibase/changelog \
  liquibase/liquibase \
  --url="jdbc:postgresql://db:5432/mydb" \
  --changeLogFile=db.changelog.xml \
  --username=postgres --password=mysecret \
  update

Generate a changelog from an existing database:

docker run --rm liquibase/liquibase \
  --url="jdbc:mysql://db:3306/app" \
  --username=root --password=pass \
  generateChangeLog

Integrate with CI/CD:

Liquibase can be included as a build step in Jenkins, GitHub Actions, or GitLab CI to apply migrations automatically during deployments.

Liquibase logs all operations to stdout and returns detailed status codes for pipeline visibility.

Image variants

Published under liquibase/liquibase, the image is available in multiple variants:

liquibase/liquibase:latest
Tracks the most recent stable release.
Ideal for local development or testing new Liquibase features.‍
liquibase/liquibase:<version>
Tagged by release version (e.g. 4.29.0, 4.25.1).
Recommended for production to ensure predictable behavior.‍
liquibase/liquibase:<version>-alpine
Lightweight variant based on Alpine Linux.
Best suited for CI/CD pipelines where size and speed matter.

Liquibase images are updated regularly with new database drivers and security fixes. For stable deployments, pin to a specific versioned tag.

Interested in base images that start and stay clean?

Oops! Something went wrong while submitting the form.