Open mayank-agarwal-96 opened 5 years ago
Issue-Label Bot is automatically applying the label bug
to this issue, with a confidence of 0.61. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
Duplicate of #199 ?
I think fix #234 should fix #199 the problem seems caused by a fix to #110 https://github.com/genuinetools/img/commit/b38a9eb63126413a3388f5e642c2f93ef9321908. which create a snapshot when pulling the image.
I just opened a PR to fix #199 (PR: https://github.com/genuinetools/img/pull/326) but that will not resolve this exactly. The layer digests do match exactly but the root digest does not if the image has Docker config schema and not an OCI config schema. In my PR, on pull, the schema is converted to an OCI schema, so the digest will change but most of the metadata is still retained.
I think my PR is still a good step forward cause it gets pull
retaining any config. I'm not sure how important it is to folks to retain the identical Docker schemas...
When I do
img pull busybox
andimg ls
, the digest issha256:05313277ba61c604f48dbe9915100d47f6b6a1d2051a82bd0590b6372e91f8a9
while when I do docker pull, the digest issha:f79f7a10302c402c052973e3fa42be0344ae6453245669783a9e16da3d56d5b4
. Both manifests are present in/.local/share/img/runc/native/content/blobs/sha256
. They each point to different config file. The one img uses misses on many fields including path, environment variables exported in the Docker image.Contents of the two digest: