Closed yosifkit closed 4 months ago
Thanks for reporting @yosifkit 👍
Alternatively, providing an updated Dockerfile with FROM eclipse-temurin:11-jre-jammy should be enough to fix the build and let it rebuild for base image updates but not move to a new JRE or Ubuntu release.
I'm gonna take this route as the safest (https://github.com/docker-library/official-images/pull/15544#discussion_r1361708245).
Describe the bug
zookeeper:3.7.2
is failing to (re)build in Docker Official Images after the parent image was updated.To Reproduce Because the
library/zookeeper
file is still pointing at https://github.com/31z4/zookeeper-docker/commit/dd520cb108da9eafe6914dce4e5dbd4877dd2411 for3.7.2
(https://github.com/docker-library/official-images/blob/6c99e13a4748dae454be260479d9a2ed51cd6c38/library/zookeeper#L5-L7), the3.7.2
image now fails to build because the parenteclipse-temurin:11-jre
has moved to Ubuntu Noble which has anubuntu
user at1000
by default now (https://github.com/docker-library/official-images/pull/17231#issuecomment-2245772484).Expected behavior
docker build
finishes and creates an image.System configuration
docker version cli:
27.0.3
, server:27.0.2
though it shouldn't matter too much as long as it is relatively up to date.Additional context I think official images just needs the updated commit for
3.7.2
though I am not sure if you also wanted thejre17
bump or not (https://github.com/31z4/zookeeper-docker/commit/5076660820c73f3b119cbdd1267c25a1e29cbbf4). Alternatively, providing an updated Dockerfile withFROM eclipse-temurin:11-jre-jammy
should be enough to fix the build and let it rebuild for base image updates but not move to a new JRE or Ubuntu release.