Updated Python manifest for Python Alpine #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Re-generated manifest to include changes made for Alpine versions of Python package (i.e. use alpine 3.5)
|
This should be opened on the base repo; https://github.com/docker-library/official-images. Looks like @tianon got it in docker-library#2508 |
tianon
added a commit
that referenced
this pull request
Mar 21, 2023
We ran into a race condition that we _think_ might be GC related, but we don't want automatic GC generally anyhow so we'll just disable this entirely and keep our eyes open for that race to resurface.
$ printf 'FROM ubuntu:20.04\n' | docker buildx build --builder bashbrew-arm64v8 --output type=oci --build-arg BUILDKIT_SYNTAX=docker/dockerfile:1@sha256:7f44e51970d0422c2cbff3b20b6b5ef861f6244c396a06e1a96f7aa4fa83a4e6 --provenance=mode=max --sbom generator=docker/buildkit-syft-scanner:stable-1@sha256:71c6aab70e25388abf054da2eaaf121727e3a4f464ddfb1987052b83c9419949 --platform linux/arm64/v8 - > oci.tar
#1 [internal] load .dockerignore
#1 transferring context: 2B done
#1 DONE 0.0s
#2 [internal] load build definition from Dockerfile
#2 transferring dockerfile: 55B done
#2 DONE 0.0s
docker-library#3 resolve image config for docker.io/docker/dockerfile:1@sha256:7f44e51970d0422c2cbff3b20b6b5ef861f6244c396a06e1a96f7aa4fa83a4e6
docker-library#3 DONE 0.1s
docker-library#4 docker-image://docker.io/docker/dockerfile:1@sha256:7f44e51970d0422c2cbff3b20b6b5ef861f6244c396a06e1a96f7aa4fa83a4e6
docker-library#4 resolve docker.io/docker/dockerfile:1@sha256:7f44e51970d0422c2cbff3b20b6b5ef861f6244c396a06e1a96f7aa4fa83a4e6 done
docker-library#4 DONE 0.0s
docker-library#4 docker-image://docker.io/docker/dockerfile:1@sha256:7f44e51970d0422c2cbff3b20b6b5ef861f6244c396a06e1a96f7aa4fa83a4e6
docker-library#4 CACHED
docker-library#5 resolve image config for docker.io/docker/buildkit-syft-scanner:stable-1@sha256:71c6aab70e25388abf054da2eaaf121727e3a4f464ddfb1987052b83c9419949
docker-library#5 DONE 0.1s
docker-library#6 [internal] load metadata for docker.io/library/ubuntu:20.04
docker-library#6 DONE 0.6s
docker-library#7 docker-image://docker.io/docker/buildkit-syft-scanner:stable-1@sha256:71c6aab70e25388abf054da2eaaf121727e3a4f464ddfb1987052b83c9419949
docker-library#7 resolve docker.io/docker/buildkit-syft-scanner:stable-1@sha256:71c6aab70e25388abf054da2eaaf121727e3a4f464ddfb1987052b83c9419949 0.0s done
docker-library#7 DONE 0.0s
docker-library#8 [linux/arm64] generating sbom using docker.io/docker/buildkit-syft-scanner:stable-1@sha256:71c6aab70e25388abf054da2eaaf121727e3a4f464ddfb1987052b83c9419949
docker-library#8 CACHED
docker-library#9 [1/1] FROM docker.io/library/ubuntu:20.04@sha256:24a0df437301598d1a4b62ddf59fa0ed2969150d70d748c84225e6501e9c36b9
docker-library#9 resolve docker.io/library/ubuntu:20.04@sha256:24a0df437301598d1a4b62ddf59fa0ed2969150d70d748c84225e6501e9c36b9 0.0s done
docker-library#9 DONE 0.0s
docker-library#10 exporting to oci image format
docker-library#10 exporting layers done
docker-library#10 exporting manifest sha256:7ee27ad7ace5741767778121ad82066c09383c68e462efcfaad124cc074b48a8 0.0s done
docker-library#10 exporting config sha256:b559481b22258f45e33c28e36cab179693b1d6ca1bfa8d7acf2b068cd61d4b39 done
docker-library#10 ERROR: content digest sha256:a774dfcdedc7c7c4f0009ddadc2f33557d60452450684534df5625f9693df81a: not found
------
> exporting to oci image format:
------
ERROR: failed to solve: content digest sha256:a774dfcdedc7c7c4f0009ddadc2f33557d60452450684534df5625f9693df81a: not found
tianon
added a commit
that referenced
this pull request
Sep 26, 2024
Support for this was implemented in my images back in tianon/dockerfiles@8c85466 as a PoC (and support for it was kept in tianon/dockerfiles@2b78191 when the explicit 0.13 builds were added), and I've actually been using it pretty heavily since without issue, both locally *and* for all of my `tianon/xxx` personal image builds (including building of `tianon/buildkit` itself, for maximum meta 😂). The primary benefit is that we get the exact same architecture support matrix as our BuildKit images (and the same set of applied patches, if they happen to impact the frontend code as well). $ docker buildx build --pull --no-cache --build-arg BUILDKIT_SYNTAX=tianon/buildkit:0.13 - <<<$'FROM bash\nRUN echo see, it works!' #0 building with "default" instance using docker driver #1 [internal] load build definition from Dockerfile #1 transferring dockerfile: 71B done #1 DONE 0.0s #2 [internal] load .dockerignore #2 transferring context: 2B done #2 DONE 0.0s docker-library#3 resolve image config for docker.io/tianon/buildkit:0.13 docker-library#3 DONE 0.2s docker-library#4 docker-image://docker.io/tianon/buildkit:0.13@sha256:95db7c7b47f142af3fe0cae7de217996dadde8c44ef9e331ddd564857ca277ab docker-library#4 resolve docker.io/tianon/buildkit:0.13@sha256:95db7c7b47f142af3fe0cae7de217996dadde8c44ef9e331ddd564857ca277ab 0.0s done docker-library#4 CACHED docker-library#5 [internal] load metadata for docker.io/library/bash:latest docker-library#5 DONE 0.2s docker-library#6 [1/2] FROM docker.io/library/bash:latest@sha256:ce062497c248eb1cf4d32927f8c1780cce158d3ed0658c586a5be7308d583cbb docker-library#6 CACHED docker-library#7 [2/2] RUN echo see, it works! see, it works! docker-library#7 DONE 0.3s docker-library#8 exporting to image docker-library#8 exporting layers 0.0s done docker-library#8 writing image sha256:ceb5fb7b6904a68eeedd25c253e54e9ae1160c404c7e9fbb26c142d8a8143ef8 done docker-library#8 DONE 0.0s
tianon
added a commit
that referenced
this pull request
Sep 30, 2024
Support for this was implemented in my images back in tianon/dockerfiles@8c85466 as a PoC (and support for it was kept in tianon/dockerfiles@2b78191 when the explicit 0.13 builds were added), and I've actually been using it pretty heavily since without issue, both locally *and* for all of my `tianon/xxx` personal image builds (including building of `tianon/buildkit` itself, for maximum meta 😂). The primary benefit is that we get the exact same architecture support matrix as our BuildKit images (and the same set of applied patches, if they happen to impact the frontend code as well). $ docker buildx build --pull --no-cache --build-arg BUILDKIT_SYNTAX=tianon/buildkit:0.13 - <<<$'FROM bash\nRUN echo see, it works!' #0 building with "default" instance using docker driver #1 [internal] load build definition from Dockerfile #1 transferring dockerfile: 71B done #1 DONE 0.0s #2 [internal] load .dockerignore #2 transferring context: 2B done #2 DONE 0.0s docker-library#3 resolve image config for docker.io/tianon/buildkit:0.13 docker-library#3 DONE 0.2s docker-library#4 docker-image://docker.io/tianon/buildkit:0.13@sha256:95db7c7b47f142af3fe0cae7de217996dadde8c44ef9e331ddd564857ca277ab docker-library#4 resolve docker.io/tianon/buildkit:0.13@sha256:95db7c7b47f142af3fe0cae7de217996dadde8c44ef9e331ddd564857ca277ab 0.0s done docker-library#4 CACHED docker-library#5 [internal] load metadata for docker.io/library/bash:latest docker-library#5 DONE 0.2s docker-library#6 [1/2] FROM docker.io/library/bash:latest@sha256:ce062497c248eb1cf4d32927f8c1780cce158d3ed0658c586a5be7308d583cbb docker-library#6 CACHED docker-library#7 [2/2] RUN echo see, it works! see, it works! docker-library#7 DONE 0.3s docker-library#8 exporting to image docker-library#8 exporting layers 0.0s done docker-library#8 writing image sha256:ceb5fb7b6904a68eeedd25c253e54e9ae1160c404c7e9fbb26c142d8a8143ef8 done docker-library#8 DONE 0.0s
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Re-generated manifest to include changes made for Alpine versions of Python package (i.e. use alpine 3.5)