ktock / container-bootfs Goto Github PK

Container image converter aiming to minimize image size and speed up boot time dramatically with block-level de-dupliction and lazy-pull technology.

License: Apache License 2.0

Dockerfile 0.90% Makefile 0.45% C 92.32% Shell 6.32%

casync container container-image de-duplication desync lazy-pull

container-bootfs's People

Contributors

Stargazers

Watchers

Forkers

renzhengeek mc256

container-bootfs's Issues

Is this project still WIP?

Checked on stargz-snapshotter which is awesome. With dedup it will even boost the whole development process, writing code and deploy in no time.

image metadata

How to deal with image metadata?
if a host want to run a image A, how does it know image A store in remote blob store or not?

rootfs

suppose that the image B which generated by our image converter mkimage, and our original image was named B.

First, when we run a image which blobs are stored on SSH server, we need to specify something like:

sudo docker run -it --privileged --device /dev/fuse \
                --volumes-from ${LOCAL_CACHE_NAME} \
                -e BLOB_STORE=ssh://foo@bar/baz \
                -e DROPBEAR_PASSWORD=foobarbaz \
                image-a:latest

now the container's rootfs was the image a's roots, right? how it change to the origin image B's rootfs(which made by blobs store on remote)? how to deal with the rootfs's change? does it need to chroot again?

Recommend Projects