No description, website, or topics provided.
Go Shell Makefile
Switch branches/tags
Nothing to show
Clone or download
rhatdan Merge pull request #199 from giuseppe/allow-to-override-conf-file
storage: allow to use a different configuration file
Latest commit 124de68 Jul 16, 2018
Permalink
Failed to load latest commit information.
cmd/containers-storage Add Store.ContainerSize() May 30, 2018
docs storage: rename fuse_program to mount_program Jul 16, 2018
drivers Merge pull request #199 from giuseppe/allow-to-override-conf-file Jul 16, 2018
hack ci: install ostree Jun 29, 2018
opts Replace deprecated repo 'github.com/docker/engine-api' Jan 17, 2018
pkg ostree: new package Jun 29, 2018
tests tests: add test for ostree deduplication Jun 29, 2018
vagrant vagrant: install ostree Jun 29, 2018
vendor storage: add ostree files Jun 29, 2018
.dockerignore Add vendor/pkg to .dockerignore Dec 5, 2015
.gitignore Update packages to match latest code in moby/pkg Sep 12, 2017
.mailmap Fix double entry in authors Jun 3, 2016
.travis.yml Fix an inconsistent indentation in .travis.yml May 21, 2018
AUTHORS Fix double entry in authors Jun 3, 2016
CONTRIBUTING.md Change cri-o IRC channel to container-projects in CONTRIBUTING.md Oct 26, 2017
LICENSE Update LICENSE date Dec 31, 2015
Makefile overlay: new option to support ostree deduplication Jun 29, 2018
NOTICE Update LICENSE date Dec 31, 2015
README.md Potential contributors need to find the CONTRIBUTOR information. Jul 5, 2018
VERSION Clean up the build machinery Jul 18, 2016
Vagrantfile Vagrantfile: update to Fedora 28 Jun 29, 2018
containers.go Improve duplicate name error message on container create Jun 19, 2018
containers_ffjson.go Improve duplicate name error message on container create Jun 19, 2018
errors.go Add LayerParentOwners()/ContainerParentOwners() Apr 3, 2018
images.go Add mapped top layers to images May 30, 2018
images_ffjson.go Update generated files May 30, 2018
layers.go Only try to copy new layers/images/containers if we create them May 7, 2018
layers_ffjson.go Update generated files May 30, 2018
lockfile.go lockfile: reshape for multiplatform Jan 30, 2018
lockfile_darwin.go lockfile: reshape for multiplatform Jan 30, 2018
lockfile_linux.go lockfile: reshape for multiplatform Jan 30, 2018
lockfile_unix.go lockfile: reshape for multiplatform Jan 30, 2018
lockfile_windows.go lockfile: reshape for multiplatform Jan 30, 2018
storage.conf storage: rename fuse_program to mount_program Jul 16, 2018
store.go storage: rename fuse_program to mount_program Jul 16, 2018
vendor.conf storage: add ostree files Jun 29, 2018

README.md

storage is a Go library which aims to provide methods for storing filesystem layers, container images, and containers. A containers-storage CLI wrapper is also included for manual and scripting use.

To build the CLI wrapper, use 'make build-binary'.

Operations which use VMs expect to launch them using 'vagrant', defaulting to using its 'libvirt' provider. The boxes used are also available for the 'virtualbox' provider, and can be selected by setting $VAGRANT_PROVIDER to 'virtualbox' before kicking off the build.

The library manages three types of items: layers, images, and containers.

A layer is a copy-on-write filesystem which is notionally stored as a set of changes relative to its parent layer, if it has one. A given layer can only have one parent, but any layer can be the parent of multiple layers. Layers which are parents of other layers should be treated as read-only.

An image is a reference to a particular layer (its top layer), along with other information which the library can manage for the convenience of its caller. This information typically includes configuration templates for running a binary contained within the image's layers, and may include cryptographic signatures. Multiple images can reference the same layer, as the differences between two images may not be in their layer contents.

A container is a read-write layer which is a child of an image's top layer, along with information which the library can manage for the convenience of its caller. This information typically includes configuration information for running the specific container. Multiple containers can be derived from a single image.

Layers, images, and containers are represented primarily by 32 character hexadecimal IDs, but items of each kind can also have one or more arbitrary names attached to them, which the library will automatically resolve to IDs when they are passed in to API calls which expect IDs.

The library can store what it calls metadata for each of these types of items. This is expected to be a small piece of data, since it is cached in memory and stored along with the library's own bookkeeping information.

Additionally, the library can store one or more of what it calls big data for images and containers. This is a named chunk of larger data, which is only in memory when it is being read from or being written to its own disk file.

Contributing Information about contributing to this project.