I'm running Bless Native Node through Docker and I'm receiving both output at the same time " Host Error " & "Node Peer"

[Psiyolbin]

{"level":"debug","component":"host","error":"failed to dial: failed to dial 12D3KooWGU96zcS8wSd8u2438qrc7L7CYGayAh6DEyaAYCDDiTA9: no good addresses\n * [/ip4/127.0.0.1/tcp/9527] dial to self attempted\n * [/ip4/172.17.0.2/tcp/9527] dial to self attempted","peer":"12D3KooWGU96zcS8wSd8u2438qrc7L7CYGayAh6DEyaAYCDDiTA9","time":"2025-04-16T18:35:46Z","message":"could not connect to discovered peer"}
{"level":"debug","component":"node","peer":"12D3KooWGuBya7RYHTzZmR7uLJYUXffSPuBUPKnmYSfsgwyjqFuw","type":"MsgHealthCheck","pipeline":"pubsub:blockless/b7s/general","time":"2025-04-16T18:35:48Z","message":"received message from peer"}

[dmikey]

All good, the following message indicates you are receiving incoming requests. The error just means there's a cross dial problem from an advertised peer.!

[Psiyolbin]

Sir I'm also facing issue while I'm trying to Store Identity Locally. Please guide me about it so i can store my node identity locally.

[dmikey]

are you running a docker image, or bare metal?

[Psiyolbin]

Docker image

[qcbred]

I got the same issue

[Maelkum]

Sir I'm also facing issue while I'm trying to Store Identity Locally. Please guide me about it so i can store my node identity locally.

Hi @Psiyolbin! In order to store node identity locally you first need to generate a private key using keyforge utility (in the release archive for b7s it's called b7s-keyforge. Using this tool you can generate a private key by running b7s-keyforge -o /path/where/key/will/be/created.

You can then feed this key to the b7s Docker instance by mounting the key inside the container, and by specifying the key path, for example:

docker run -d --name b7s \
  -e NODE_KEY_PATH=/app/worker/key.bin \
  -v /path/to/private/key.bin:/app/worker/key.bin

(some arguments excluded for brevity)

[Wanbogang]

is there an option to link nodes with our account sir?