mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
399695305c
When pulling an image by platform, it is possible for the image's configured platform to not match what was in the manifest list. The image itself is buggy because either the manifest list is incorrect or the image config is incorrect. In any case, this is preventing people from upgrading because many times users do not have control over these buggy images. This was not a problem in 19.03 because we did not compare on platform before. It just assumed if we had the image it was the one we wanted regardless of platform, which has its own problems. Example Dockerfile that has this problem: ```Dockerfile FROM --platform=linux/arm64 k8s.gcr.io/build-image/debian-iptables:buster-v1.3.0 RUN echo hello ``` This fails the first time you try to build after it finishes pulling but before performing the `RUN` command. On the second attempt it works because the image is already there and does not hit the code that errors out on platform mismatch (Actually it ignores errors if an image is returned at all). Must be run with the classic builder (DOCKER_BUILDKIT=0). Signed-off-by: Brian Goff <cpuguy83@gmail.com> |
||
---|---|---|
.. | ||
cache.go | ||
image.go | ||
image_builder.go | ||
image_commit.go | ||
image_delete.go | ||
image_events.go | ||
image_exporter.go | ||
image_history.go | ||
image_import.go | ||
image_inspect.go | ||
image_prune.go | ||
image_pull.go | ||
image_push.go | ||
image_search.go | ||
image_search_test.go | ||
image_tag.go | ||
image_unix.go | ||
image_windows.go | ||
images.go | ||
locals.go | ||
service.go | ||
store.go | ||
store_test.go |