update Dockerfile tools

[johnsonjie]

1. Purpose or design rationale of this PR

...

2. PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
• ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
• docs: Documentation-only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

3. Deployment tag versioning

Has the version in params/version.go been updated?

• This PR doesn't involve a new deployment, git tag, docker image tag, and it doesn't affect traces
• Yes

4. Breaking change label

Does this PR have the breaking-change label?

• This PR is not a breaking change
• Yes

Summary by CodeRabbit

• Chores
  • Docker image build updated to include additional system utilities (netcat, curl) and to clean installation artifacts for a slimmer final image.
  • Project patch version bumped to .14 to reflect the latest release.

[coderabbitai]

Walkthrough

The Dockerfile's Ubuntu stage now installs netcat-openbsd and curl alongside ca-certificates, and removes /var/lib/apt/lists/* after installation. The params package patch version constant VersionPatch was incremented from 13 to 14.

Changes

Cohort / File(s)	Summary
Docker image dependencies and cleanup Dockerfile	Added netcat-openbsd and curl to the apt install line and appended rm -rf /var/lib/apt/lists/* to clean apt lists after installation.
Version bump params/version.go	Incremented public constant VersionPatch from 13 to 14. No other version fields changed.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Pay attention to params/version.go to ensure the version bump is intended and consistent with release notes or changelog.
• Verify the Dockerfile apt cleanup is correct for all intended base image stages and doesn't remove needed files in other layers.

Poem

🐇 A rabbit's note on tiny tweaks:
Soft packages hop into the nest,
Curl and netcat join the rest,
Apt crumbs swept clean, the image light—
Patch grows by one, a quiet bite. 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'update Dockerfile tools' is related to the changeset (adding packages to Dockerfile), but it's vague and doesn't clearly indicate what specific tools were added or why, making it only partially specific.	Revise the title to follow conventional commits format (e.g., 'fix: add netcat-openbsd and curl to Docker image') for clarity and consistency with repository standards.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description check	✅ Passed	The PR description follows the required template structure with section headings and checklist items completed, though the 'Purpose or design rationale' section contains only placeholder ellipses (...) and lacks actual substantive content.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/update-Dockerfile

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 02c5b35 and dea1c24.

📒 Files selected for processing (1)

• params/version.go (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: test
• GitHub Check: Analyze (go)

🔇 Additional comments (1)

params/version.go (1)

27-27: Verify the necessity of the version bump for Dockerfile-only changes.

The PR description explicitly states "This PR doesn't involve a new deployment, git tag, docker image tag", yet VersionPatch is incremented from 13 to 14. The diff shows only two changes: Dockerfile (adds netcat-openbsd, curl) and the version increment—no other functional changes. Adding tools to a Dockerfile is a build/infrastructure change that typically does not warrant a patch version bump unless those tools are essential for a critical fix in the Go codebase.

Please clarify:

1. Is this version bump intentional, or was it accidentally included?
2. Should the PR description be updated to reflect an intended deployment/release, or should the version increment be removed?

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[kchangn]

lgtm I guess we need geth team's approval as well

[Thegaram]

lgtm, bumped version for easier deployment