Skip to content

add port conflict notice for exsiting BN tip #108

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.

Sign up for GitHub

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

Merged
ksale001 merged 2 commits into from
Feb 24, 2026
Merged

add port conflict notice for exsiting BN tip #108

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d08643c
add port conflict notice for exsiting BN tip
nickh-obol Jan 30, 2026
6fe75f7
Merge branch 'main' into nick/add-multi-charon-tip
ksale001 Feb 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions run-a-dv/start/create-a-dv-with-a-group.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -479,8 +479,8 @@ CHARON_BEACON_NODE_ENDPOINTS=<YOUR_REMOTE_BEACON_NODE_URL>
...
```
{% hint style="info" %}
If your existing beacon node is running in another CDVN instance on the same Docker host, you can access it by specifying
`http://host.docker.internal:5052` as the endpoint.
If your existing beacon node is running in a another CDVN instance on the same Docker host, you can access it by specifying
`http://host.docker.internal:5052` as the endpoint. Note: You will need to change the charon p2p port in the .env file (`CHARON_PORT_P2P_TCP=`) of the second CDVN stack to avoid port conflict.
{% endhint %}
3. Uncomment `EL=el-none` and `CL=cl-none` variables in the `.env` file and comment `EL=el-nethermind` and `CL=cl-lighthouse` variables:

Expand Down