yosifkit

Does `php:8.3-fpm-bullseye` work? (instead of the default, which is Debian Bookworm-based)

I guess that this is likely due to seccomp -- so, need to update Docker, runc, and libseccomp on your host. https://github.com/docker-library/python/issues/837#issuecomment-1599640563

>How long do you plan to provide bullseye based images? We'll have `bullseye` based images until the next Debian stable major release (`trixie`). It doesn't have a release date but,...

> However, this `wget "https://get.helm.sh/helm-v3.10.3-linux-amd64.tar.gz"` will succeed in an alpine image like `alpine:3.18.2`. The `busybox` image is as close to upstream BusyBox releases as we can; the `busybox` binary in...

It didn't run because the access for @docker-library-bot to push was revoked so we removed the job: https://github.com/docker-library/oi-janky-groovy/commit/c1d73ec8bfb6a2a7b1f053df32fc3d340506b0b5

This sounds similar to https://github.com/docker-library/redis/issues/365 and https://github.com/docker-library/python/issues/837. The default Debian just moved from Bullseye to Bookworm. So the root cause is likely `libseccomp`: https://github.com/docker-library/python/issues/837#issuecomment-1599640563. You can continue to use the...

Closing since there is not anything that can be done in the image to mitigate an SELinux denial.

> The good news is that these don't show up on https://hub.docker.com/_/jruby anymore! > > (The bad news is that they _do_ still show up on https://hub.docker.com/search?q=jruby&image_filter=official 🙈) This seems...

I'm not sure when the `mips64le` image for 3.10.8 will be fixed. It looks like a linker issue, so we might have to file a bug upstream after some more...

It comes from the `pip` install layer. We could delete it, but it seems like there is a bug in `get-pip.py`.