celestia-node icon indicating copy to clipboard operation
celestia-node copied to clipboard

docker: Potential issues with bootstrapping when running node in docker on macos

Open vlad2095 opened this issue 1 year ago • 17 comments

Celestia Node version

0308aea76857ff27484946fce99004ebf10a3cb8 / v0.13.7

OS

ghcr.io/celestiaorg/celestia-node container on MacOS M1.

Install tools

docker/podman

Others

No response

Steps to reproduce it

celestia light init --p2p.network celestia --core.ip rpc.celestia.pops.one celestia light start --p2p.network celestia --core.ip rpc.celestia.pops.one

Expected result

successfully running light node

Actual result

Error: node: failed to start: header/p2p: failed to open a new stream: failed to dial: failed to dial 12D3KooWQpuTFELgsUypqp9N4a1rKBccmrmQVY8Em9yhqppTJcXf: all dials failed

  • [/ip4/163.172.132.189/tcp/2121] dial backoff

Relevant log output

2024-06-18T06:08:16.254Z        INFO    node    nodebuilder/module.go:26        Accessing keyring...
2024-06-18T06:08:16.275Z        INFO    badger4 [email protected]/levels.go:171   All 1 tables opened in 1ms
2024-06-18T06:08:16.276Z        INFO    badger4 [email protected]/discard.go:66   Discard stats nextEmptySlot: 1
2024-06-18T06:08:16.276Z        INFO    badger4 [email protected]/db.go:368       Set nextTxnTs to 143
2024-06-18T06:08:17.150Z        INFO    pidstore        pidstore/pidstore.go:67 Loaded peers from disk  {"amount": 0}
2024-06-18T06:08:17.150Z        INFO    module/header   header/config.go:66     No trusted peers in config, initializing with default bootstrappers as trusted peers
2024-06-18T06:08:17.170Z        INFO    header/p2p      p2p/subscriber.go:81    joining topic   {"topic ID": "/celestia/header-sub/v0.0.1"}
2024-06-18T06:08:17.170Z        INFO    header/p2p      p2p/exchange.go:99      client: starting client {"protocol ID": "/celestia/header-ex/v0.0.3"}
2024-06-18T06:08:17.170Z        INFO    pidstore        pidstore/pidstore.go:67 Loaded peers from disk  {"amount": 0}
2024-06-18T06:08:17.468Z        INFO    pidstore        pidstore/pidstore.go:84 Persisted peers successfully    {"amount": 0}
2024-06-18T06:08:17.468Z        WARN    header/p2p      p2p/subscriber.go:92    unregistering validator: no validator for topic /celestia/header-sub/v0.0.1
2024-06-18T06:08:17.468Z        INFO    basichost       basic/natmgr.go:112     DiscoverNAT error:no NAT found
2024-06-18T06:08:17.469Z        INFO    badger4 [email protected]/db.go:546       Lifetime L0 stalled for: 0s

2024-06-18T06:08:17.476Z        INFO    badger4 [email protected]/db.go:625       
Level 0 [ ]: NumTables: 00. Size: 0 B of 0 B. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 16 MiB
Level 1 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 2 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 3 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 4 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 5 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 6 [B]: NumTables: 01. Size: 3.5 KiB of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level Done
Error: node: failed to start: header/p2p: failed to open a new stream: failed to dial: failed to dial 12D3KooWQpuTFELgsUypqp9N4a1rKBccmrmQVY8Em9yhqppTJcXf: all dials failed
  * [/ip4/163.172.132.189/tcp/2121] dial backoff

Notes

While I tried to run light node in any of p2p networks, it fails to connect via p2p

However, it seems like network-related issue, 'cause when I used mobile internet provider, it successfully started. I remember having similar issue in one of my projects, where we solved it by increasing p2p timeout a bit.

Is it possible to configure celestia with increased p2p timeout or solve the issue in some other way?

vlad2095 avatar Jun 27 '24 11:06 vlad2095