Repository navigation
[java-docker] Add multi-platform Java 25 runtime with Docker CLI - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a dedicated
ossyupiik/java-dockerbase for Java applications that control an external Docker Engine, without changing the existing Zulu images or their release workflow./usr/local/bin/dockerfrom the official Docker CLI image to/usr/bin/docker; no Docker daemon, DinD entrypoint, plugins or provisioning script.linux/amd64andlinux/arm64under one published reference.10001:10001,HOME=/tmp, no entrypoint andjava --version; support a read-only root filesystem with writable/tmp.java-docker/25.0.5-alpine3.24-docker29.9.2, after both native tests pass. No publishing from PRs, main pushes or manual runs.This is a dispatcher/runtime base, not an agent development-toolchain image: no Maven, gh, javac or Docker plugins are included. Docker socket access remains an explicitly provisioned, host-administration capability.
Validation performed locally
git diff --check: passed.Native ARM64 execution is not available on the local host and must be confirmed by the included native ARM64 CI job. No Docker Engine socket was mounted, no image/tag was published, and no vulnerability or attestation audit is claimed.
Release prerequisites
Provision
ossyupiik/java-dockeron Docker Hub and ensure the existingDOCKERHUB_USERNAME/DOCKERHUB_TOKENsecrets can publish to it. After merge and successful native CI, push a matching release tag, then use the reported multi-platform index digest in consumers such as Jib.