Offline Installation

Pigsty installs from Internet upstream by default, but some envs are isolated from the Internet. To address this, Pigsty supports offline installation using offline packages. Think of them as Linux-native Docker images.

Overview

Offline packages bundle all required RPM/DEB packages and dependencies; they are snapshots of the local APT/YUM repo after a normal installation.

In serious prod deployments, we strongly recommend using offline packages. They ensure all future nodes have consistent software versions with the existing env, and avoid online installation failures caused by upstream changes (quite common!), guaranteeing you can run it independently forever.

Offline Packages

We typically release offline packages for the following Linux distros, using the latest OS minor version.

If you use an OS from the list above (exact minor version match), we recommend using offline packages. Pigsty provides ready-to-use pre-made offline packages for these systems, freely downloadable from GitHub.

You can download matching assets from the GitHub release page; offline package filenames follow this pattern, and v4.3.0 checksums will be completed after the final release:

b1924a907f3db2411109745cc03f4316  pigsty-pkg-v4.3.0.d12.aarch64.tgz
20b71530b96c8c611dcd6b0a052c67de  pigsty-pkg-v4.3.0.d12.x86_64.tgz
e1d0ac623a608c749158803616aaeced  pigsty-pkg-v4.3.0.d13.aarch64.tgz
27b6360815ff234db0376338d1ce944f  pigsty-pkg-v4.3.0.d13.x86_64.tgz
08cde469c86017c14f808fd127e51a87  pigsty-pkg-v4.3.0.el10.aarch64.tgz
371c1d5229b1584650bda42a570cdc47  pigsty-pkg-v4.3.0.el10.x86_64.tgz
07472f5069f92c96d6b65147e0658c26  pigsty-pkg-v4.3.0.el9.aarch64.tgz
153e2dc5904171975babd1d2dbcce480  pigsty-pkg-v4.3.0.el9.x86_64.tgz
70a3a4faecfc4691ee9b528b8c35ee08  pigsty-pkg-v4.3.0.u22.aarch64.tgz
6968bc55aedcff922cff59b5893f3e12  pigsty-pkg-v4.3.0.u22.x86_64.tgz
59699d34aaaf178a12a044740f4cc56e  pigsty-pkg-v4.3.0.u24.aarch64.tgz
935666f192390d52cbde0593e2e253dc  pigsty-pkg-v4.3.0.u24.x86_64.tgz
84ef45377c5a6fac7f7285ebd7a71404  pigsty-pkg-v4.3.0.u26.x86_64.tgz

Using Offline Packages

Offline installation steps:

1. Download Pigsty offline package, place it at /tmp/pkg.tgz
2. Download Pigsty source package, extract and enter directory (assume extracted to home: cd ~/pigsty)
3. ./bootstrap, it will extract the package and configure using local repo (and install ansible from it offline)
4. ./configure -g -c rich, you can directly use the rich template configured for offline installation, or configure yourself
5. Run ./deploy.yml as usual—it will install everything from the local repo

If you want to use the already extracted and configured offline package in your own config, modify and ensure these settings:

• repo_enabled: Set to true, will build local software repo (explicitly disabled in most templates)
• node_repo_modules: Set to local, then all nodes in the env will install from the local software repo
  • In most templates, this is explicitly set to: node,infra,pgsql, i.e., install directly from these upstream repos.
  • Setting it to local will use the local software repo to install all packages, fastest, no interference from other repos.
  • If you want to use both local and upstream repos, you can add other repo module names too, e.g., local,node,infra,pgsql

The first parameter, if enabled, Pigsty will create a local software repo. The second parameter, if contains local, then all nodes in the env will use this local software repo. If it only contains local, then it becomes the sole repo for all nodes. If you still want to install other packages from other upstream repos, you can add other repo module names too, e.g., local,node,infra,pgsql.

Hybrid Installation Mode

If your environment has Internet access, there’s a hybrid approach that combines the advantages of offline and online installation. You can use the offline package as a base, and supplement missing packages online.

For example, if you’re using RockyLinux 9.6 but the official offline package is for RockyLinux 9.7. You can use the el9 offline package (though made for 9.7), then execute make repo-build before formal installation to re-download missing packages for 9.6. Pigsty will download the required increments from upstream repos.

Making Offline Packages

If your OS isn’t in the default list, you can make your own offline package with the built-in cache.yml playbook:

1. Find a node running the exact same OS version with Internet access
2. Use rich config template to perform online installation (configure -c rich)
3. cd ~/pigsty; ./cache.yml: make and fetch the offline package to ~/pigsty/dist/${version}/
4. Copy the offline package to the env without Internet access (ftp, scp, usb, etc.), extract and use via bootstrap

We offer paid services providing tested, pre-made offline packages for specific Linux major.minor versions (¥200).

Bootstrap

Pigsty relies on ansible to execute playbooks; this script is responsible for ensuring ansible is correctly installed in various ways.

./bootstrap       # Ensure ansible is correctly installed (if offline package exists, use offline installation and extract first)

Usually, you need to run this script in two cases:

• You didn’t install Pigsty via the installation script, but by downloading or git clone of the source package, so ansible isn’t installed.
• You’re preparing to install Pigsty via offline packages and need to use this script to install ansible from the offline package.

The bootstrap script will automatically detect if the offline package exists (-p to specify, default is /tmp/pkg.tgz). If it exists, it will extract and use it, then install ansible from it. If the offline package doesn’t exist, it will try to install ansible from the Internet. If that still fails, you’re on your own!

./bootstrap -k # or --keep