Liquibase Workertools

Liquibase Workertools is a ready-to-run Docker image that packages Liquibase, the open-source tool for versioning and deploying database schema changes, as an…

  • Databases
  • Development
Liquibase Workertools is a ready-to-run Docker image that packages Liquibase, the open-source tool for versioning and deploying database schema changes, as an Octopus Deploy worker. It bundles everything needed to run Liquibase reliably so teams can apply and automate their database schema changes without manually setting up the tool on their own servers.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

76/100 Good

Maintained
100last commit 25 days ago
Popular
755,637 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
801 GB minimum RAM, runs on ARM
GitHub stars
5,637
Open issues
271
Last commit
2026-10-27
Latest release
v5.0.4
Activity
declining

Checked 18 days ago - source: GitHub (liquibase/liquibase)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 1 CPU core(s), 300 MB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Add the database driver you need If you run Liquibase in Docker and connect to a database, add the matching driver, for example by setting INSTALL_MYSQL=true for MySQL or using lpm add mysql in a Dockerfile. Liquibase 5 does not include most database drivers by default, so without the right driver it cannot connect to your database. source
  • List every changelog folder in search path If your changelog files are in more than one folder, set LIQUIBASE_SEARCH_PATH to list all of them, including the current folder if you expect it to be used. That variable tells Liquibase where to look for changelogs, and it does not automatically include the current folder, so missing folders can cause changelogs to be ignored. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why does my self-hosted Liquibase container fail to connect to a database?

Liquibase 5 does not include most database drivers by default. Add the matching driver, for example by setting INSTALL_MYSQL=true for MySQL or using lpm add mysql in a Dockerfile.

Why are some changelog folders ignored by my self-hosted Liquibase run?

Set LIQUIBASE_SEARCH_PATH to list every changelog folder that should be used, including the current folder if needed, because the current folder is not included automatically.

Where should I look if a Liquibase change set does not roll back correctly?

The Liquibase troubleshooting section includes guidance for rollback issues.

Is SQLPlus authentication failure covered when Liquibase is configured with runWith: sqlplus?

Yes, the Liquibase troubleshooting section lists SQLPlus failing with ORA-01017 when using runWith: sqlplus.

Answers sourced from github.com, support.liquibase.com

Community

Collected 48 days ago - public community threads