Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for getting archive of container rootfs changes #9839

Open
jlhawn opened this issue Dec 29, 2014 · 3 comments
Open

Add support for getting archive of container rootfs changes #9839

jlhawn opened this issue Dec 29, 2014 · 3 comments
Labels
area/api area/builder area/distribution exp/expert kind/enhancement Enhancements are not bugs or new features but can improve usability or performance.

Comments

@jlhawn
Copy link
Contributor

jlhawn commented Dec 29, 2014

The docker export command and corresponding API endpoint allow the client to get an archive of the container's root filesystem. This is useful for squashing an entire set of image layers into one, but there's currently no way to get just the file system diff for a container.

This could be achieved by adding an optional parameter to the container export API endpoint and an optional flag to the docker export command: diff=1 This would instruct the runtime to only return the layer diff for the container rather than the entire filesystem.

Why is this useful?

It would allow for additional functionality in tools which are used to build images like the docker build command. Layer archives could be collected by the client, checksums computed for each layer archive, and for images to be built using a new content-addressable format.

@jessfraz jessfraz added kind/enhancement Enhancements are not bugs or new features but can improve usability or performance. exp/expert labels Feb 26, 2015
@stevvooe
Copy link
Contributor

#11104 was a PR for this function by hacking the "docker save" output. It would be somewhat nice to have access to individual layers by id. Not sure how this would integrate but the concept is sound.

@LK4D4
Copy link
Contributor

LK4D4 commented Sep 14, 2016

@tonistiigi @stevvooe Do you think this is still actual?

@stevvooe
Copy link
Contributor

@LK4D4 I think there is still a general need to be able to access layers from an API on the daemon. There is a solution to this problem that involves integrating a registry and providing other access paths to registry data, such as uncompressed hash identifiers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api area/builder area/distribution exp/expert kind/enhancement Enhancements are not bugs or new features but can improve usability or performance.
Projects
None yet
Development

No branches or pull requests

4 participants