vi7al/regbroom repository overview

⁠Docker Registry Broom - make your registry clean again!

Regbroom tool cleans up Docker Registry image tags by specified release (e.g. X.Y.Z) and development version (e.g. X.Y.Z-bla.1) patterns keeping only specified amount of the most recently published tags.

Dev version tag keep logic is the following: keep specified in the config amount of dev tags per kept release tag (substring match) OR just keep specified amount of dev tags from the whole list of tags matching dev pattern if no release tags found and force flag is specified in the repo config.

latest Dockerfile⁠

⁠Usage

Prepare Regbroom config.yaml (see details in the Configuration⁠ section) and then run:

docker run --rm \
  -v /path/to/regbroom/config.yaml:/root/.config/regbroom/config.yaml
  vi7al/regbroom

⁠Configuration

⁠Config options and examples

See config_local.yaml⁠ for options description and some handy configuration examples. The same file is present in the Docker image at /root/.config/regbroom/config_example.yaml

⁠Advanced configuration

⁠Using non HTTPS/TLS Docker registries

Dockerized Regbroom

By default Regbroom Docker image comes with the example of insecure registries config for the regctl tool. This could be found in the docker/regctl_config.json⁠

If you need to tell regctl to not use HTTPS for some other real registries this could be achieved via following ways:

• permanent way: change mentioned json config and build custom Regbroom Docker image
• runtime way: prepare your custom regctl config.json using regctl registry set <registry> --tls disabled and mount this custom config as an additional volume:

  docker run --rm \
    -v /etc/regbroom:/root/.config/regbroom \  # Regbroom config volume
    -v "$HOME"/.regctl/config.json:/root/.regctl/config.json \  # custom regctl config.json
    vi7al/regbroom
  

  Copy

⁠Development

⁠Releasing the image

Go to the repo⁠ and change whatever is needed

Bump the version in the ci/build.env⁠

Create Merge Request and add maintainers from Dockerfile⁠ as reviewers

After MR is reviewed, checked by CI and merged to the master run:

git checkout master && git pull --rebase
make git-tag git-push

CI will be triggered automatically now and release Docker image to the Registry