Stay at Searching peers

This is my startup command

./setup.sh --dataDir mainnet-data --elClient geth --network mainnet --dockerWithSudo --withTerminal

result
`Mar-15 07:25:59.873[execution] info: Execution client urls=http://localhost:8551
INFO [03-15|07:26:07.001] Looking for peers peercount=2 tried=42 static=0
INFO [03-15|07:26:17.082] Looking for peers peercount=2 tried=34 static=0
Mar-15 07:27:36.070[network] info: running libp2p instance in worker thread
Mar-15 07:27:43.098[network] info: libp2p worker started peer=16Uiu2HAm9143nyyy1ase5WhCRMnmLmb6XQoyzY4ds1wMkjeGvxfm
Mar-15 07:27:44.902[network] info: PeerId 16Uiu2HAm9143nyyy1ase5WhCRMnmLmb6XQoyzY4ds1wMkjeGvxfm, Multiaddrs /ip4/0.0.0.0/tcp/9000
Mar-15 07:27:45.250[rest] info: Started REST API server address=http://0.0.0.0:9596
Mar-15 07:27:45.251[rest] warn: REST API server is exposed, ensure untrusted traffic cannot reach this API
Mar-15 07:27:45.253[] info: Searching peers - peers: 0 - slot: 8638636 - head: (slot -300) 0xd083…0ac0 - exec-block: syncing(19438558 0x5cb2…) - finalized: 0x7a59…49fd:269946
Mar-15 07:27:44.889[network] info: discv5 worker started peerId=16Uiu2HAm9143nyyy1ase5WhCRMnmLmb6XQoyzY4ds1wMkjeGvxfm, initialENR=enr:-IO4QI-Y_RQMsfZ0x_2udy0NXIfnFNQetISW387JJhaUfoypKCY0Z_fbT9_2H4rOa1zfWz93IR_b1lM-tPnvMvyTwq8BgmlkgnY0iXNlY3AyNTZrMaECybUM2hh6HgQF6WCpi5uId1dlLqBSFeymPtuARyPT89yDdGNwgiMog3VkcIIjKA, bindAddr4=/ip4/0.0.0.0/udp/9000
Mar-15 07:27:53.002[] warn: Low peer count peers=0
Mar-15 07:27:53.003[] info: Searching peers - peers: 0 - slot: 8638637 - head: (slot -301) 0xd083…0ac0 - exec-block: syncing(19438558 0x5cb2…) - finalized: 0x7a59…49fd:269946
Mar-15 07:28:05.006[] info: Searching peers - peers: 0 - slot: 8638638 - head: (slot -302) 0xd083…0ac0 - exec-block: syncing(19438558 0x5cb2…) - finalized: 0x7a59…49fd:269946`

Start with setup.sh and reproduce the command shown in the issue, then inspect the startup logs around libp2p, discv5, and the repeated “Searching peers” messages. Determine whether the node progresses beyond peers: 0 and document the relevant behavior or configuration needed for peer discovery to complete.

Written by the indexing model from the issue text.