Skip to content

Conversation

@fkondej
Copy link

@fkondej fkondej commented Jan 9, 2026

No description provided.

@fkondej fkondej self-assigned this Jan 9, 2026
"--http-allow-origin", "*",
"--disable-packet-filter",
"--target-peers", "0",
"--target-peers", "1",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why is this necessary? I remember at some point if target peers was not 0, the beacon node would wait for the number of peers before returning as healthy, which would create problems for non builder-hub deploymnets.

Copy link
Author

Choose a reason for hiding this comment

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

To clarify the setup:

  • Playground runs reth + lighthouse in Docker
  • VM adds a second reth + lighthouse pair that needs to sync with playground
  • need to support both: playground with VM and without VM

Current behavior:

  • --target-peer 0: VM's lightouse doesn't connect to the playground
  • --target-peer 1: Vm works, but you mentioned this breaks non-VM setup

I've tried --subscribe-all-subnets with --target-peers 0 but VM still doesn't connect.

Do you know a config that would work for both VM and non-VM setups?

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.

3 participants