Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: docker-compose RPC ports should only listen on loopback #524

Merged
merged 3 commits into from
Nov 19, 2022

Conversation

b5
Copy link
Member

@b5 b5 commented Nov 18, 2022

@b5 b5 added this to the v0.1.1 milestone Nov 18, 2022
@b5 b5 requested review from Arqu and ramfox November 18, 2022 22:15
@b5 b5 self-assigned this Nov 18, 2022
@b5 b5 marked this pull request as ready for review November 18, 2022 22:16
Copy link
Collaborator

@Arqu Arqu left a comment

Choose a reason for hiding this comment

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

Think we got ports mixed up there. Other than that LGTM

- "4401:4401"
- "4444:4444"
# RPC port, iroh CLI uses this to control your p2p service
Copy link
Collaborator

Choose a reason for hiding this comment

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

Think it's the inverse here. 4401 is the RPC port. 4444 is the libp2p port.

@b5 b5 merged commit 8471e49 into main Nov 19, 2022
@b5 b5 deleted the b5/docker_compose_loopback branch November 19, 2022 02:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

make sure docker compose example doesn't expose writeable APIs
2 participants