feat(docker): modernize and harden the multi-architecture node workflow - #6928
Closed
3for wants to merge 3 commits into
Closed
feat(docker): modernize and harden the multi-architecture node workflow#69283for wants to merge 3 commits into
3for wants to merge 3 commits into
Conversation
Build source-aligned amd64 and arm64 images with a direct non-root FullNode entrypoint. Harden local and remote build contexts, configuration handling, runtime mounts, lifecycle operations, JVM defaults, and deployment guidance.
Add path-aware amd64 and arm64 image builds, remote-source coverage, persistent BuildKit caches, and a fail-closed aggregate gate. Cover Docker helper behavior, image invariants, launcher parsing, lifecycle operations, and build-context filtering.
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.
What does this PR do?
Why are these changes required?
The existing Docker workflow had fallen behind current java-tron development. It ran nodes as root, lacked consistent multi-architecture validation, and could use configuration from a different source than the node binary.
These changes provide a safer, reproducible, and maintainable first-party Docker workflow.
This PR has been tested by:
Unit Tests
Manual Testing
umaskchecksFollow up
start.shhardening in a separate PR.Extra details
This is a compatibility-affecting change. Existing data created by root-based images may require a one-time ownership migration.
The helper defaults to a locally built image because the current official
latestimage does not meet the new non-root runtime contract. Nile nodes should continue using the Nile-specific repository andtron-dockerworkflow.This PR builds and validates images but does not publish them.