You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The image info file keys off of the image's Dockerfile folder path. In the case of the sample projects, there can be a single Dockerfile that is built on multiple platforms, each producing different tags. So when the image info file gets updated with the metadata from these images, that metadata all goes into the same element since the images all share the same Dockerfile folder path. This doesn't currently cause any issues with the image dependency flow system because it only looks up the digests for the images that it cares about and ignores the extraneous other data in the image info file. But from a correctness standpoint, the metadata contained in the image info file should be separated properly.
The text was updated successfully, but these errors were encountered:
mthalman
changed the title
Image info format doesn't separate metadata for images built with Dockerfiles in same folder
Image info format doesn't separate metadata for multiples images built from the same Dockerfile
Aug 28, 2019
The image info file keys off of the image's Dockerfile folder path. In the case of the sample projects, there can be a single Dockerfile that is built on multiple platforms, each producing different tags. So when the image info file gets updated with the metadata from these images, that metadata all goes into the same element since the images all share the same Dockerfile folder path. This doesn't currently cause any issues with the image dependency flow system because it only looks up the digests for the images that it cares about and ignores the extraneous other data in the image info file. But from a correctness standpoint, the metadata contained in the image info file should be separated properly.
The text was updated successfully, but these errors were encountered: