yosifkit
yosifkit
Assuming that `mysql:8.4.0-oraclelinux8` fixes the problem: If there are enough users requiring the orcalelinux8-based image because of CPU restrictions, it might make sense for us to continue to build both...
Confirmed that Oracle Linux 9 requires the `x86-64-v2` [microarchitecture level](https://en.wikipedia.org/wiki/X86-64#Microarchitecture_levels) ([docs.oracle.com](https://docs.oracle.com/en/operating-systems/oracle-linux/9/relnotes9.0/ol9-AboutOracleLinux9.html#ol9-features-architecture)): > ### Available Architectures > The release is available for installation on the following platforms: >- Intel® 64-bit (x86_64)...
> but for some reason the 8.0 tag now points to a different image Every active tag in official images can and will be updated to point to an image...
As promised in the upstream conversation, a contrib module has materialized (thanks to `effulgentsia`). So, the answer is to add https://www.drupal.org/project/sqlite337 to your Drupal site. I am not yet sure...
Closing old issue; seems resolved.
Yes, this happened with https://github.com/docker-library/meta-scripts/pull/93. We finally have switched all our builds over to `buildkit`, so they now include attached provenance (the item with `unknown` os and architecture in the...
All the architecture specific repos as listed in the [readme](https://github.com/docker-library/official-images/blob/c71143d61e6b854e5958ce0c765c3e18243b5616/README.md#architectures-other-than-amd64) are official images as much as the empty namespace (aka `library/`) is. The `library/` images are just the combination of...
Like @tianon's comment, the arch specific repos are still useful to avoid the platform vector matching that is used when pulling multi-arch images. In other words, to guarantee getting a...
Your options for getting an updated `setuptools` or clean scan (https://github.com/docker-library/python/issues/1012#issuecomment-2736331135): > You will either need to either: > 1. Update to Python 3.12 or newer (which no longer bundles...
> is 666 a bug then, and the expected file permission for COPY from git context is 600? It *should* be `644` for "regular" files and if the file does...