Serve your container images from a read-only registry.

cartorio allows you to serve content from your local filesystem through the Docker HTTP V2 Registry API.

It currently supports the following filesystem formats:

• docker tarball (what you get from docker save)
• OCI image layout
• rootfs tarball / directory
• Concourse image_resource

Table of Contents

• Usage
  • Docker
  • Kubernetes
• Scope
• LICENSE

The usage of cartorio requires only two steps:

1. loading one or more container image(s) from a directory or tarball, then
2. serving those container images to those implementing the Docker Registry HTTP API v2.

# save one (or more container images) from a docker 
# daemon to a tarball
docker save one-image another-image > image.tar


# load the image into a format that `cartorio` understands
# and is able to use to serve the contents
cartorio load --tarball=./image.tar


# serve the images
cartorio serve


# pull the image from cartorio
docker pull $MACHINE_IP:5000/one-image
docker pull $MACHINE_IP:5000/another-image

Being cartorio a tool that can serve any amount of container images, the use of cartorio with Kubernetes can fit multiple purposes, more interestingly:

• providing the necessary infratructure images for bootstrapping an airgapped Kubernetes cluster, and
• in a single container, distribute images that can't be retrieved fr

cartorio's scope is limited only to:

• loading images into its blobstore for serving, and
• serving container images that have been preloaded.

Apache License 2.0 - see LICENSE.