Skip to content
Store application configuration files in Docker/OCI registries
Go Shell
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
cmd/imgpkg init Nov 1, 2019
docs minor readme tweaks Nov 1, 2019
hack init Nov 1, 2019
pkg/imgpkg init Nov 1, 2019
test/e2e init Nov 1, 2019
vendor init Nov 1, 2019
.gitignore init Nov 1, 2019
CONTRIBUTING.md init Nov 1, 2019
Gopkg.lock init Nov 1, 2019
Gopkg.toml init Nov 1, 2019
LICENSE init Nov 1, 2019
NOTICE
README.md include example snippet in main readme Nov 1, 2019

README.md

imgpkg

imgpkg (pronounced: image package) allows to store sets of files (e.g. application configuration) as images in Docker (OCI) registries. This may be a good alternative to storing files in other places as Docker registry already keeps your other images. Original primary use case for this CLI was to store application configuration (i.e. templates) as an image.

$ imgpkg push -i your-user/app1-config:0.1.1 -f config/
$ imgpkg pull -i your-user/app1-config:0.1.1 -o /tmp/app1-config
$ imgpkg tag ls -i your-user/app1-config

Features:

  • Allows to push image containing set of files
  • Allows to pull image and extract set of files
  • Allows to list pushed image tags
  • Uses Docker layer media type to work with existing registries
  • Uses deterministic file permissions and timestamps to make images reproducable (same digest if nothing changed)

Development

./hack/build.sh

eval $(minikube docker-env)
docker login
export IMGPKG_E2E_IMAGE=dkalinin/test-simple-content
./hack/test-all.sh
You can’t perform that action at this time.