fix: align op-node RPC listener with Docker port mapping - #54
Open
Lesnak1 wants to merge 1 commit into
Open
Conversation
Lesnak1
marked this pull request as ready for review
August 9, 2026 21:15
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
95457545Problem
The
rise-nodeservice publishes7545:9545, so Docker forwards host port7545to port9545inside the container. However, the service command overrides op-node with--rpc.port=7545.That leaves Docker forwarding requests to container port
9545while op-node listens on7545, making the published rollup RPC endpoint unreachable.Fix
Set
--rpc.port=9545so the in-container listener matches the Compose target port. The user-facing host port remains7545.Verification
maincommit+1/-17545→ container9545; op-node listener9545git diff --check