- Task
- Version ยท 6.0.2
- Create
Install Liquibase Secure server in a restricted or air-gapped network
Last updated: November 17, 2026
This article is the alternative to Install Liquibase Secure server, for organizations that vet vendor images before anything runs and for server hosts with no internet access. You copy the Liquibase Secure server images into your own container registry, check them there, and install the server from your copy. Liquibase takes no part in that process and needs nothing configured on your registry.
The pull command makes the copy. It reads the images from Liquibase with your license and pushes them to your registry with your own docker login, so the host that runs it must reach both. The host that runs the server also downloads the deployment files from Liquibase, unless you save them with pull and carry them over. With saved deployment files, it needs to reach only your registry.
Before you begin
You must have downloaded and extracted the
liquibase-platformCLI, as in step 1 of Install Liquibase Secure server.You must have the license file your Liquibase account team sends you, or a directory that holds your license files.
You must have an account on your registry that can push images, for the host that copies them, and one that can pull images, for the host that runs the server.
The host that copies the images must have
docker buildx. Docker Desktop includes it. On Linux, it can be a separate package, such asdocker-buildx-plugin.
Procedure
(Optional) Create the repositories in your registry
If your registry creates a repository on the first push, skip this step. Otherwise, create these repositories under the registry path you will copy to in step 3:
liquibase-platform-apiliquibase-platform-webliquibase-platform-migrateliquibase-platform-llt
If you will also copy the third-party images in step 3, create nginx, postgres, and redis under the same path.
Log in to your registry on the host that copies the images
On a host that can reach both Liquibase and your registry, log in to your registry with the account that can push to it. Be sure to replace your_registry_host with your registry's host name. For example, registry.example.com
docker login your_registry_hostCopy the images to your registry
--to is your registry, with an optional path, that the images go under. pull copies the release of the CLI you run, unless you pass --tag.
Be sure to:
Replace
your_license_filewith the path to your license file, or to the directory that holds your license files. For example,/etc/liquibase/liquibase.licReplace
your_registry_pathwith your registry and the path to copy the images under. For example,registry.example.com/liquibase-platform
./liquibase-platform pull --license your_license_file --to your_registry_pathpull copies these images, each under the release's version tag:
Copied to | Contents |
| The API |
| The web console |
| The database migrations |
| The license- |
Each image is copied by digest, with every platform it was built for, so the copy is byte for byte the image Liquibase published. pull compares the digest it pushed with the source's digest and stops if they differ. It prints each image's digest as it goes, so you can match what you vet with what you run. When it finishes, it prints the install command to run from the copy.
If you also want to vet and run nginx, PostgreSQL, and Redis from your registry, add --include-third-party. The deployment runs these images from Docker Hub by default.
./liquibase-platform pull --license your_license_file --to your_registry_path --include-third-partyThey are copied by digest as well, under the last part of their Docker Hub name. For example, postgres:17.11-alpine becomes your_registry_path/postgres:17.11-alpine. Docker Hub limits anonymous pulls, so pull uses this host's docker login for Docker Hub when there is one.
If your Docker hosts already pull Docker Hub images through a registry mirror, configured as registry-mirrors in Docker, you can leave out --include-third-party. The mirror serves the third-party images. A Docker registry mirror serves Docker Hub images only, so the Liquibase images still need copying.
If the host that runs the server cannot reach Liquibase, add --files with a directory. pull saves the release's verified deployment files there, so you can carry them to the server host. Copy the third-party images too, because that host cannot reach Docker Hub either.
./liquibase-platform pull --license your_license_file --to your_registry_path --include-third-party --files ./releaseVet the images
Scan, sign, or approve the images in your registry with your own tooling, the same way you vet any other vendor image. In step 6, every Liquibase image comes from your registry, so what runs is what you vetted.
If you saved the deployment files in step 3, copy the release directory and the CLI archive to the host that runs the server.
Log in to your registry on the server host
On the host that runs the server, log in to your registry with the account that can pull from it. Be sure to replace your_registry_host with your registry's host name. For example, registry.example.com
docker login your_registry_hostInstall from your copy
Run install with --registry set to the same value you passed to --to in step 3. With --registry, install pulls the images from your registry with your docker login, and it still uses your license to download and verify the deployment files from Liquibase.
Be sure to:
Replace
your_license_filewith the path to your license file. For example,/etc/liquibase/liquibase.licReplace
your_registry_pathwith the value you passed to--toin step 3. For example,registry.example.com/liquibase-platformReplace
your_deployment_directorywith the empty directory for the deployment. For example,/opt/liquibase-platformReplace
your_fully_qualified_domain_namewith the domain name people will use to reach the server. For example,liquibase.example.com
If you copied the third-party images in step 3, add --include-third-party, so the deployment runs nginx, PostgreSQL, and Redis from your registry as well.
If the server host cannot reach Liquibase, replace --license with --files and the directory you saved in step 3. install reads the deployment files from that directory instead of downloading them. Before it writes anything, it checks that the directory holds the version it is installing, and it verifies each file's checksum and Liquibase's signature, as it does for a download. It makes no call to Liquibase.
install records your registry as IMAGE_REGISTRY in the .env file in the deployment directory, so later update runs pull from it too. To finish, back up the deployment secrets, check the server's health, create the administrator account, and import your license, as in steps 3 to 6 of Install Liquibase Secure server.
Update from your registry
To move to a new release, copy it first, vet it, and then update. Run both commands with the CLI of the new release.
Be sure to:
Replace
your_license_filewith the path to your license fileReplace
your_registry_pathwith the value you passed to--towhen you first copied the imagesReplace
your_new_versionwith the release to update to. For example,6.0.2Replace
your_deployment_directorywith the deployment directory
update pulls from the registry recorded in .env unless you pass --registry. If you installed with --include-third-party, copy the new release with --include-third-party as well. update moves each of NGINX_IMAGE, POSTGRES_IMAGE, and REDIS_IMAGE in .env that points at your registry to the version the new release runs, and leaves a value that points anywhere else as it is.
On a server host that cannot reach Liquibase, run pull with --files for the new release on the connected host, carry the directory across, and run update with --files and --tag on the server host. Upgrade Liquibase Server covers what update asks you to confirm and how to go back.