Docker builds failing since Jun 17th

Hi all,
I’ve just noticed the nightly builds for the docker images have been failing since June 17th due to some credentials issue:

https://build.geoserver.org/view/geoserver/job/geoserver-release-docker/1978/console

For those not having access to the logs:

+ docker build --build-arg WAR_ZIP_URL=https://build.geoserver.org/geoserver/2.27.x/geoserver-2.27.x-latest-war.zip --build-arg STABLE_PLUGIN_URL=https://build.geoserver.org/geoserver/2.27.x/ext-latest --build-arg COMMUNITY_PLUGIN_URL=https://build.geoserver.org/geoserver/2.27.x/community-latest --build-arg GS_VERSION=2.27-SNAPSHOT --build-arg GS_BUILD=62 --build-arg BUILD_GDAL=false -t geoserver-docker.osgeo.org/geoserver:2.27.x .
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
            Install the buildx component to build images with BuildKit:
            https://docs.docker.com/go/buildx/

Sending build context to Docker daemon  2.352MB

Step 1/94 : ARG BUILDER_BASE_IMAGE=eclipse-temurin:17.0.15_6-jdk-jammy@sha256:928978458d0a23c3c223bacb3fe55a17754a3304c8db51b99c22efe79d11f33a
Step 2/94 : ARG GEOSERVER_BASE_IMAGE=tomcat:9.0.106-jdk17-temurin-jammy@sha256:44044df3ab1c8bd4eaea4c93e3b978b3accebc3d54e6040bf6d5b2378d730229
Step 3/94 : ARG GS_VERSION=2.27.0
Step 4/94 : ARG BUILD_GDAL=false
Step 5/94 : ARG PROJ_VERSION=9.5.1
Step 6/94 : ARG GDAL_VERSION=3.10.2
Step 7/94 : ARG INSTALL_PREFIX=/usr/local
Step 8/94 : FROM $BUILDER_BASE_IMAGE AS gdal_builder
Get "https://registry-1.docker.io/v2/library/eclipse-temurin/manifests/sha256:928978458d0a23c3c223bacb3fe55a17754a3304c8db51b99c22efe79d11f33a": unauthorized: incorrect username or password
Build step 'Execute shell' marked build as failure
Finished: FAILURE

Hum… I see the credentials being tracked in Jenkins. Maybe they were modified on such date? Who might update the server with up to date credentials?

Cheers
Andrea

Hi Andrea, this tripped me up during this 2.27.2 release. I simply added Docker Hub (not docker.osgeo.org) credentials to the Docker build process, and this appeared to fix the problem (or it was coincidence :wink: )

More details: You're invited to talk on Matrix

Peter