celestia-node: `Error: node: failed to start within timeout(2m0s): context deadline exceeded`

Celestia Node version

v0.10.0

OS

ubuntu/mac

Install tools

docker and from source

Others

No response

Steps to reproduce it

docker run -e NODE_TYPE=light -e P2P_NETWORK=blockspacerace ghcr.io/celestiaorg/celestia-node:v0.10.0 celestia light start --core.ip https://rpc-blockspacerace.pops.one --gateway --gateway.addr 127.0.0.1 --gateway.port 26659 --p2p.network blockspacerace

or by installing v0.10.0 from source and starting a node

Expected result

node starts

Actual result

errors with Error: node: failed to start within timeout(2m0s): context deadline exceeded on first start. if you manually stop the first start process, and restart with same command, the node will start. this only seems to be occuring the first time, and will be successful after a retry within a few seconds.

Relevant log output

Unable to find image 'ghcr.io/celestiaorg/celestia-node:v0.10.0' locally
v0.10.0: Pulling from celestiaorg/celestia-node
c41833b44d91: Already exists 
b77e825ad173: Pull complete 
d6e91910a142: Pull complete 
9dc2d410a250: Pull complete 
1343c56d774e: Pull complete 
Digest: sha256:94c341b819b34b000862c6ffa4cd32571c2a161154173342b5dd11d396d5d62c
Status: Downloaded newer image for ghcr.io/celestiaorg/celestia-node:v0.10.0
Initializing Celestia Node with command:
celestia light init --p2p.network blockspacerace
2023-05-24T20:58:44.683Z	INFO	node	nodebuilder/init.go:28	Initializing Light Node Store over '/home/celestia/.celestia-light-blockspacerace-0'
2023-05-24T20:58:44.684Z	INFO	node	nodebuilder/init.go:60	Saved config	{"path": "/home/celestia/.celestia-light-blockspacerace-0/config.toml"}
2023-05-24T20:58:44.684Z	INFO	node	nodebuilder/init.go:62	Accessing keyring...
2023-05-24T20:58:44.686Z	WARN	node	nodebuilder/init.go:191	Detected plaintext keyring backend. For elevated security properties, consider using the `file` keyring backend.
2023-05-24T20:58:44.686Z	INFO	node	nodebuilder/init.go:206	NO KEY FOUND IN STORE, GENERATING NEW KEY...	{"path": "/home/celestia/.celestia-light-blockspacerace-0/keys"}
2023-05-24T20:58:44.692Z	INFO	node	nodebuilder/init.go:211	NEW KEY GENERATED...

NAME: my_celes_key
ADDRESS: celestia1y67gaymgmyzgla4wekqg8y945952yh75tfwgcv
MNEMONIC (save this somewhere safe!!!): 
canvas dwarf garbage reduce liar shine whale hope edge same artefact tribe crystal cup size dune slender oil human track evoke security truly popular

2023-05-24T20:58:44.692Z	INFO	node	nodebuilder/init.go:69	Node Store initialized


Starting Celestia Node with command:
celestia light start --core.ip https://rpc-blockspacerace.pops.one --gateway --gateway.addr 127.0.0.1 --gateway.port 26659 --p2p.network blockspacerace

2023-05-24T20:58:44.742Z	INFO	node	nodebuilder/module.go:22	Accessing keyring...
2023-05-24T20:58:44.745Z	INFO	module/state	state/keyring.go:40	constructed keyring signer	{"backend": "test", "path": "/home/celestia/.celestia-light-blockspacerace-0/keys", "key name": "my_celes_key", "chain-id": "blockspacerace-0"}
2023-05-24T20:58:44.746Z	WARN	module/gateway	gateway/module.go:25	Gateway is enabled, however gateway endpoints are not authenticated. Use with caution!
2023-05-24T20:58:44.829Z	INFO	badger	v2@v2.2007.4/levels.go:183	All 0 tables opened in 0s

2023/05/24 20:58:45 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details.
2023-05-24T20:58:45.196Z	INFO	module/header	header/config.go:58	No trusted peers in config, initializing with default bootstrappers as trusted peers
2023-05-24T20:58:45.202Z	INFO	header/p2p	p2p/exchange.go:84	client: starting client	{"protocol ID": "/blockspacerace-0/header-ex/v0.0.3"}
2023-05-24T20:58:45.203Z	INFO	fraudserv	fraudserv/helpers.go:29	joining topic	{"id": "/blockspacerace-0/fraud-sub/badencoding/v0.0.1"}
2023-05-24T20:58:45.203Z	INFO	fraudserv	fraudserv/service.go:97	starting fraud proof service	{"protocol ID": "/blockspacerace-0/fraud/v0.0.1"}
2023-05-24T20:58:46.203Z	INFO	share/discovery	discovery/discovery.go:253	discovering peers	{"want": 5}
2023-05-24T20:58:47.610Z	INFO	canonical-log	swarm/swarm_dial.go:500	CANONICAL_PEER_STATUS: peer=12D3KooWNsTQo4WHqGMkupHvNL1Fa4kVUMVkzRzCBqiopAfAmcbC addr=/ip4/91.107.209.69/udp/2121/quic-v1 sample_rate=100 connection_status="established" dir="outbound"
2023-05-24T20:58:50.183Z	INFO	basichost	basic/natmgr.go:93	DiscoverNAT error:no NAT found
2023-05-24T20:58:52.638Z	INFO	canonical-log	swarm/swarm_dial.go:500	CANONICAL_PEER_STATUS: peer=12D3KooWSgzwyhPuXsdKecbLYdGD9mf3Mmkr3UkKVrpyANE99Vxq addr=/ip4/91.229.245.186/udp/2121/quic-v1 sample_rate=100 connection_status="established" dir="outbound"
2023-05-24T20:58:53.433Z	INFO	canonical-log	swarm/swarm_dial.go:500	CANONICAL_PEER_STATUS: peer=12D3KooWBTkqApC8aG1LCBYxuG55nkushCasaGbp66y6Mk4ada32 addr=/ip4/157.90.21.139/udp/2121/quic-v1 sample_rate=100 connection_status="established" dir="outbound"
2023-05-24T20:59:55.637Z	INFO	share/discovery	discovery/discovery.go:315	discovered wanted peers	{"amount": 5}
2023-05-24T21:00:45.204Z	INFO	badger	v2@v2.2007.4/db.go:1027	Storing value log head: {Fid:0 Len:29 Offset:1777}

Error: node: failed to start within timeout(2m0s): context deadline exceeded

Notes

No response