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
I have found a bug that the documentation does not mention anything about my problem
I have found a bug that there are no open or closed issues that are related to my problem
I have provided version/information about my environment and done my best to provide a reproducer
Description of bug
Bug description
Images built with Buildkit 0.20.0 may differ from the ones built with Buildkit 0.19.0, because a new "variant" field may be added in the config blob of the image. Personally, I've seen this happen only when building ARM images.
Here's a side by side diff of two config blobs. Left is Buildkit v0.19.0, and right is Buildkit v0.20.0:
If you untar the image.tar tarballs, and check the config blog, you'll see that the "variant": "v8" field is present only in the tarball produced by Buildkit v0.20.0.
Version information
I have reproduced this both locally and in GitHub actions (docker/setup-buildx-action@v3). Here's the version information of the latter:
Contributing guidelines and issue reporting guide
Well-formed report checklist
Description of bug
Bug description
Images built with Buildkit 0.20.0 may differ from the ones built with Buildkit 0.19.0, because a new "variant" field may be added in the config blob of the image. Personally, I've seen this happen only when building ARM images.
Here's a side by side diff of two config blobs. Left is Buildkit v0.19.0, and right is Buildkit v0.20.0:
diff -y config.b19 config.b20 { { "architecture": "arm64", "architecture": "arm64", "config": { "config": { "Env": [ "Env": [ "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin "DEBIAN_FRONTEND=noninteractive" "DEBIAN_FRONTEND=noninteractive" ], ], "Cmd": [ "Cmd": [ "bash" "bash" ] ] }, }, "created": "2023-02-28T21:21:00Z", "created": "2023-02-28T21:21:00Z", "history": [ "history": [ { { "created": "2023-09-07T00:39:39.206776845Z", "created": "2023-09-07T00:39:39.206776845Z", "created_by": "/bin/sh -c #(nop) ADD file:fb5c8f411c4a1 "created_by": "/bin/sh -c #(nop) ADD file:fb5c8f411c4a1 }, }, { { "created": "2023-09-07T00:39:39.650056081Z", "created": "2023-09-07T00:39:39.650056081Z", "created_by": "/bin/sh -c #(nop) CMD [\"bash\"]", "created_by": "/bin/sh -c #(nop) CMD [\"bash\"]", "empty_layer": true "empty_layer": true }, }, { { "created": "2023-02-28T21:21:00Z", "created": "2023-02-28T21:21:00Z", "created_by": "ENV DEBIAN_FRONTEND=noninteractive", "created_by": "ENV DEBIAN_FRONTEND=noninteractive", "comment": "buildkit.dockerfile.v0", "comment": "buildkit.dockerfile.v0", "empty_layer": true "empty_layer": true }, }, { { "created": "2023-02-28T21:21:00Z", "created": "2023-02-28T21:21:00Z", "created_by": "RUN /bin/sh -c repro-sources-list.sh && "created_by": "RUN /bin/sh -c repro-sources-list.sh && "comment": "buildkit.dockerfile.v0" "comment": "buildkit.dockerfile.v0" } } ], ], "os": "linux", "os": "linux", "rootfs": { "rootfs": { "type": "layers", "type": "layers", "diff_ids": [ "diff_ids": [ "sha256:341de903723838835820feffc6ff0ab04ea7ffddd3886cd "sha256:341de903723838835820feffc6ff0ab04ea7ffddd3886cd "sha256:cdc84d7fdc4c77e4965366c040d1e0aae36b6adba12d7e2 "sha256:cdc84d7fdc4c77e4965366c040d1e0aae36b6adba12d7e2 ] ] } | }, > "variant": "v8" } }
Purpose of this bug report:
Reproduction
Dockerfile: https://github.com/reproducible-containers/repro-sources-list.sh/blob/master/Dockerfile.debian-12
Command to build image with Buildkit 0.19.0:
Command to build image with Buildkit 0.20.0:
If you untar the
image.tar
tarballs, and check the config blog, you'll see that the"variant": "v8"
field is present only in the tarball produced by Buildkit v0.20.0.Version information
I have reproduced this both locally and in GitHub actions (
docker/setup-buildx-action@v3
). Here's the version information of the latter:Docker info:
The text was updated successfully, but these errors were encountered: