Skip to content

fix(docker): update image builds and improve deployment tooling - #6981

Open
3for wants to merge 4 commits into
tronprotocol:release_v4.8.3from
3for:feat/docker
Open

3for wants to merge 4 commits into
tronprotocol:release_v4.8.3from
3for:feat/docker

Conversation

@3for

@3for 3for commented Sep 18, 2026

Copy link
Copy Markdown
Collaborator

What does this PR do?

  • Update Docker images to Ubuntu 24.04, verify the amd64 JDK with PGP, and launch FullNode directly.
  • Improve helper argument handling, configuration, mounts, port mappings and container lifecycle management.
  • Add static CI checks and refresh deployment guides, including JVM sizing examples.

Why are these changes required?

The Docker deployment path used outdated dependencies, weak JDK verification and stale instructions, with no dedicated CI coverage.

This PR has been tested by:

  • Unit Tests: Java unit tests not run; no Java code changes.
  • Manual Testing: Bash syntax validation (bash -n) and ShellCheck passed.

Follow up

  • Sync matching Dockerfiles to develop and verify standalone helper builds for both architectures.
  • Address JVM defaults, helper memory options, and vmoptions parsing/runtime compatibility separately.

Extra details

Targets release_v4.8.3. Until develop receives the matching files, use a complete checkout for --build. Dockerfiles continue to build Java sources from remote master.

Comment thread docker/docker.md Outdated

These commands rerun the build steps without deleting existing build caches.

When the script is used from a java-tron checkout, only the Dockerfile and build context are resolved relative to `docker.sh`, regardless of the current working directory. The current checkout's Java sources are not added to that context. If only `docker.sh` was downloaded, the required architecture-specific Dockerfile is downloaded into a temporary build context and removed after the build. Both paths build the remote `master` branch.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[SHOULD] Please document the standalone build limitation here. The helper downloads only the Dockerfile from develop, but the current Dockerfile still requires docker-entrypoint.sh, which is missing from the temporary build context.

The PR description already acknowledges the pending synchronization. Until that is completed, this guide should instruct users to build from a complete checkout containing the matching Dockerfiles.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@317787106 Resolved in 56e778c.

- Explain that downloaded Dockerfiles require a missing docker-entrypoint.sh
- Direct users to a complete checkout containing matching Dockerfiles
- Document synchronization and verification requirements for standalone builds
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

4 participants