Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
docker history reports missing container ids after upgrade to 1.10 #20131
After upgrade to docker 1.10.0 output of the
As you can see only the top image id is reported properly. Note that this issue is not image specific, output like that we get for all our images.
This result has been observed on both VirtualBox and Rackspace Cloud Server.
The following output was obtained from a Rackspace Cloud Server:
I think this is expected; the content-addressable storage no longer uses "parent" images to chain the image-layers together. Newly pulled images also no longer will show the intermediate images (these "missing" images will only be shown for images that were present on the host, but have been migrated to the new storage)
/cc @tonistiigi just for checking; but I think this is expected.
(perhaps we need to mention this in the migration wiki https://github.com/docker/docker/wiki/Engine-v1.10.0-content-addressability-migration)
Hmm, but those layers still have ids, right (inferred from content or not), so why not show them?
Here is the problem: imagine we have
@horkhe There is no way to do this securely(the previous method wasn't secure either). We can expose the layer IDs in
referenced this issue
Feb 12, 2016
Sorry, I don't totally know how the internals work, but does there currently exist a workaround? By that I mean, can I pull an image, then run it at a layer other than the top layer? (I basically use this for testing purposes, its certainly possible to build the image myself then do it, but its slightly less convenient)