Open dboreham opened 1 year ago
Noticed this in passing. It may be ok, but seems odd:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 92238e24ab8b cerc/fixturenet-eth-lighthouse:local "/opt/testnet/run.sh" 27 minutes ago Up 26 minutes (healthy) laconic-7213d90c4a50766399994db216868224-fixturenet-eth-lighthouse-2-1 d4723db9b5db cerc/fixturenet-eth-lighthouse:local "/opt/testnet/run.sh" 27 minutes ago Up 26 minutes (healthy) 0.0.0.0:63790->8001/tcp laconic-7213d90c4a50766399994db216868224-fixturenet-eth-lighthouse-1-1 ad417ceae82b cerc/fixturenet-eth-geth:local "/opt/testnet/run.sh" 27 minutes ago Up 27 minutes (healthy) 8545-8546/tcp, 30303/tcp, 30303/udp laconic-7213d90c4a50766399994db216868224-fixturenet-eth-geth-2-1 c68c732e8bd0 cerc/fixturenet-eth-geth:local "/opt/testnet/run.sh" 27 minutes ago Up 27 minutes (healthy) 8546/tcp, 30303/tcp, 30303/udp, 0.0.0.0:63765->8545/tcp laconic-7213d90c4a50766399994db216868224-fixturenet-eth-geth-1-1 e9b82cd779a7 cerc/fixturenet-eth-lighthouse:local "/opt/testnet/run.sh" 27 minutes ago Up 27 minutes laconic-7213d90c4a50766399994db216868224-fixturenet-eth-bootnode-lighthouse-1 ca9c7c34359a cerc/fixturenet-eth-geth:local "/opt/testnet/run.sh" 27 minutes ago Up 27 minutes 8545-8546/tcp, 30303/udp, 0.0.0.0:63764->9898/tcp, 0.0.0.0:63763->30303/tcp laconic-7213d90c4a50766399994db216868224-fixturenet-eth-bootnode-geth-1
bootnode-lighthouse-1 and eth-lighthouse-2-1 have no ports.
It turned out that the containers with no mapped ports were ok (no need for the host to ever communicate with them), but we should fix all cases where we have fixed mappings for ports.
Noticed this in passing. It may be ok, but seems odd:
bootnode-lighthouse-1 and eth-lighthouse-2-1 have no ports.