-
Notifications
You must be signed in to change notification settings - Fork 773
Open
Description
Describe the bug
When trying to build from the Dockerfile at docker/server/Dockerfile it throws following error:
docker buildx build --platform linux/amd64 -t ghcr.io/<****>/conductor:test-v1 -f docker/server/Dockerfile --push .
[+] Building 2.1s (4/4) FINISHED docker-container:dreamy_austin
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 2.58kB 0.0s
=> ERROR [internal] load metadata for docker.io/library/openjdk:17-bullseye 2.1s
=> CANCELED [internal] load metadata for docker.io/library/alpine:3.19 2.1s
=> CANCELED [internal] load metadata for docker.io/library/alpine:3.20 2.1s
------
> [internal] load metadata for docker.io/library/openjdk:17-bullseye:
------
Dockerfile:7
--------------------
5 | # 0. Builder stage 1
6 | # ===========================================================================================================
7 | >>> FROM openjdk:17-bullseye AS builder
8 |
9 | ARG INDEXING_BACKEND=elasticsearch
--------------------
ERROR: failed to solve: openjdk:17-bullseye: failed to resolve source metadata for docker.io/library/openjdk:17-bullseye: docker.io/library/openjdk:17-bullseye: not found
The dockerfile still depends on openjdk:17-bullseye which seems to be depreciated and recently removed from Docker Hub. (I couldn't find exact depreciation date, but I had last ran it on 22nd Sept 2025, it built successfully)
Details
Conductor version:
Last Commit :-
commit a9af7fa (HEAD -> main, tag: v3.21.20, origin/main, origin/HEAD)
Merge: db1fb21 954bc1b
Author: Naomi Most naomi.most@orkes.io
Date: Mon Oct 27 13:53:18 2025 -0700
To Reproduce
Steps to reproduce the behavior:
Run this at the root of the repo:
docker buildx build --platform linux/amd64 -t conductor:test-v1 -f docker/server/Dockerfile .
Expected behavior
The image builds successfully
Screenshots

Metadata
Metadata
Assignees
Labels
No labels