DKP - DocKer compose Packer

Packs existent docker-compose project in executable single encrypted (GPG AES256) archive (tar + gz). It means that you don't need to install DKP or remember procedure details during restore, which dramatically reduces stress and make your life simpler. In the end - it's hard to remember how to restore backup made by N generations of administrators years ago before you...

The pipeline is:

flowchart TD
    A[tar volumes] -->B(tar images)
    B --> C[add env files and manifests]
    C --> D[add restore scripts]
    D --> E[compress and encrypt]
    E --> F[wrap to self-extracting file]

For backup you need:

gpg
python 3.8+ (see tests in workflow)
sh
tar
gzip
docker with compose plugin

For restore you need:

gpg
sed
tar
gzip

Installation

Recommended

pip install dkp

Alternative - just download dkp/dkp.py and make it executable.

Backward compatibility

Once backup created, the version of DKP doesn't matter anymore since archive is self-complete independent file.

New DKP versions may introduce more features as well as different layout of final archive, but it will not affect previous backups.

Usage

Create backup

usage: dkp [-h] [--output OUTPUT] [--skip-images] [--all-images]
           [--passphrase PASSPHRASE] [--env-file [ENV_FILE ...]]
           [project]

Docker Compose packer - pack compose project with all batteries included

positional arguments:
  project               Compose project name. Default is docker-compose-pack

options:
  -h, --help            show this help message and exit
  --output OUTPUT, -o OUTPUT
                        Output file. Default docker-compose-pack.bin
  --skip-images, -S     Do not archive images
  --all-images          Export all images. Without this option, only the
                        images of those services are exported that have an
                        'image' key in the compose file.
  --passphrase PASSPHRASE, -p PASSPHRASE
                        Passphrase to encrypt backup. Can be set via env
                        PASSPHRASE
  --env-file [ENV_FILE ...]
                        Environment file(s) that should be passed to Compose
                        with '--env-file'

Caveat: The --env-file option works according to the default behavior of the argparse module, not according to the Docker CLI conventions.

You should pass the --env-file option only once, and enumerate the files afterwards (--env-file env1 env2). If you write --env-file env1 --env-file env2, the second option overwrites the first, and only env2 is used.
You can use -- before the project name when you use --env-file before it. This might be necessary because --env-file env project means that you have two env files (one called env and the other called project).

Restore