Skip to content

Commit 2a85cb3

Browse files
Aleksandr ZamiatinAleksandr Zamiatin
authored andcommitted
another small change
1 parent 6101868 commit 2a85cb3

File tree

1 file changed

+19
-18
lines changed

1 file changed

+19
-18
lines changed

docs/operators/operator-node/maintenance/troubleshooting.md

Lines changed: 19 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,8 @@ ssv-pulse:
9595
# - '--network=holesky' # Add this if you run a Holesky Node
9696
# - '--platform linux/arm64' # Add this if you run on an arm64 machine
9797
networks:
98-
- local-docker # Make sure network is the same as yours. Check with command docker network ls.
98+
- host # This allows ssv-pulse to access any docker container hosted on the machine
99+
# Alternatively, you can use your existing network instead. Check with docker network ls.
99100
pull_policy: always
100101
```
101102
@@ -104,27 +105,29 @@ Then run `docker compose up ssv-pulse` to run the benchmark tool.
104105
</TabItem>
105106
<TabItem value="docker-run" label="docker run">
106107

107-
Use the following command to run the benchmark tool:
108+
Use the following command to run the benchmark tool:
108109

109-
```bash
110-
docker run --rm --pull=always --name ssv-pulse \
111-
ghcr.io/ssvlabs/ssv-pulse:latest benchmark \
112-
--consensus-addr=REPLACE_WITH_ADDR \
113-
--execution-addr=REPLACE_WITH_ADDR \
114-
--ssv-addr=REPLACE_WITH_ADDR \
115-
--duration=60m
116-
```
117-
118-
Replace the various addresses with the respective endpoints, e.g. http://lighthouse:5052, http://geth:8545, and SSV http://ssv_node:16000 (or your other SSVAPIPort).
119-
120-
If you run a Holesky Node you should add `--network=holesky` to the command.
110+
```bash
111+
docker run --rm --network=host --pull=always --name ssv-pulse \
112+
ghcr.io/ssvlabs/ssv-pulse:latest benchmark \
113+
--consensus-addr=REPLACE_WITH_ADDR \
114+
--execution-addr=REPLACE_WITH_ADDR \
115+
--ssv-addr=REPLACE_WITH_ADDR \
116+
--duration=60m
117+
```
121118

122-
If you run this on a arm64 machine you should add `--platform linux/arm64` to the command.
119+
Replace the various addresses with the respective endpoints, e.g. `http://lighthouse:5052`, `http://geth:8545`, and SSV `http://ssv_node:16000` (or your other SSVAPIPort).
123120

121+
- If you run a Holesky Node you should add `--network=holesky` to the command.
122+
- If you run this on a arm64 machine you should add `--platform linux/arm64` to the command.
124123
</TabItem>
125124
</Tabs>
126125

127-
The tool will run for 1 hour and provide you with results as a table. An example of output is below:
126+
#### Benchmark results
127+
128+
The tool will run for 1 hour and provide you with results as a table.
129+
130+
On example below you can see low Peer connection on SSV Node, this most likely caused by closed 16000 port:
128131

129132
```log
130133
┌────────────────┬─────────────┬──────────────────────────────────────────────────────────────┬────────────┬───────────────────────────────────────────────────────────┐
@@ -157,8 +160,6 @@ The tool will run for 1 hour and provide you with results as a table. An example
157160
└────────────────┴─────────────┴──────────────────────────────────────────────────────────────┴────────────┴───────────────────────────────────────────────────────────┘
158161
```
159162

160-
The results signalize low Peer connection on SSV Node, this most probably caused by closed ports.
161-
162163
## FAQ
163164

164165
<details>

0 commit comments

Comments
 (0)