liquibase pulls statistics

DEPRECATION NOTICE

With the release of Liquibase 5.0, this repository is officially deprecated and will not receive any further releases beyond patch updates.

Users are encouraged to switch to one of the following alternatives, depending on your needs:

• liquibase/liquibase -- Community Edition under Functional Source License (if you have a valid Liquibase License Key, you should use liquibase/liquibase-secure instead) • liquibase/liquibase-secure -- Commercial version with enterprise features

As of Liquibase 5.0, the Community edition and the official Docker Community liquibase image no longer include database drivers or extensions by default. You must now explicitly add database drivers using the Liquibase Package Manager (LPM), or manually install/mount extensions into the container. See the Liquibase 5.0 Release Announcement for more details.

Quick reference

• Maintained by: Liquibase • Where to get help: the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow

Supported tags and respective Dockerfile links

• 5.0, 5.0.1, latest • 5.0-alpine, 5.0.1-alpine, alpine

Quick reference (cont.)

• Where to file issues: https://github.com/liquibase/docker/issues • Supported architectures: (more info) amd64, arm64v8 • Published image artifact details: repo-info repo's repos/liquibase/ directory (history) (image metadata, transfer size, etc) • Image updates: official-images repo's library/liquibase label official-images repo's library/liquibase file (history) • Source of this description: docs repo's liquibase/ directory (history)

What is Liquibase?

Liquibase is DevOps for your database. More information about Liquibase can be found at http://www.liquibase.org.

Liquibase compares the contents of a Change Log to the database to determine which, if any, changes need to be applied to the database. For example, you can create tables, add columns, and many more with Liquibase. Liquibase is delivered via a Docker container to assist users that are leveraging Docker for their CI/CD solution.

How to use this image

If you are executing Liquibase via the command line today, you are probably doing it like so:

The only change to use this docker image, is to use docker run ... and mount the folder containing your changelog.xml (or .yml or .json or .sql) to /liquibase/changelog in the Liquibase container

All Liquibase commands, such as rollback, updateSQL, and others, are available, as well.

Image Variants

The liquibase images come in many flavors, each designed for a specific use case.

liquibase:

This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.

liquibase:-alpine

This image is based on the popular Alpine Linux project, available in the alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.

This variant is useful when final image size being as small as possible is your primary concern. The main caveat to note is that it does use musl libc instead of glibc and friends, so software will often run into issues depending on the depth of their libc requirements/assumptions. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.

To minimize image size, it's uncommon for additional related tools (such as git or bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the alpine image description for examples of how to install packages if you are unfamiliar).

License

View license information for the Liquibase software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's liquibase/ directory.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

Description from the Docker Hub listing.