README.md 4.8 KB

Note: this is the "per-architecture" repository for the arm32v5 builds of the liquibase official image -- for more information, see "Architectures other than amd64?" in the official images documentation and "An image's source changed in Git, now what?" in the official images FAQ.

Quick reference

Supported tags and respective Dockerfile links

WARNING: THIS IMAGE IS NOT SUPPORTED ON THE arm32v5 ARCHITECTURE

Quick reference (cont.)

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.

logo

How to use this image

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

$ liquibase update --driver=org.postgresql.Driver --url="jdbc:postgresql://<DATABASE_IP>:<DATABASE_PORT>/<DATABASE>" --changeLogFile=/liquibase/changelog/changelog.xml --username=<USERNAME> --password=<PASSWORD>

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

$ docker run -v /home/user/changelog:/liquibase/changelog arm32v5/liquibase --driver=org.postgresql.Driver --url="jdbc:postgresql://<DATABASE_IP>:<DATABASE_PORT>/<DATABASE>" --changeLogFile=/liquibase/changelog/changelog.xml --username=<USERNAME> --password=<PASSWORD>

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

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.