[DEVNET] Issue with Starting Devent due to Default cl_type: lighthouse in Documentation

[opfocus]

In the current documentation examples , it seems that it is not possible to start the devnet.
The possible reason is that the default L1 setting is set to:

cl_type: lighthouse

After adding the following configuration, it starts up properly:

ethereum_package:
  participants:
    - cl_type: teku

Additionally, both the following files have cl_type: teku set:

• Line 57 of network_params.yaml
• Lines 71C5-71C20 of simple.yaml
• kt-devnet: switch to geth-teku for l1 optimism#14305

I am unsure about the reason why cl_type: lighthouse fails to start, and I hope an investigation can be conducted. Alternatively, I suggest replacing it with teku in the documentation example. Another possible solution would be to direct users to the kurtosis-devnet example.

Attached is the error encountered while running the example on Ubuntu 24.04.

There was an error executing Starlark code

An error occurred executing instruction (number 29) at github.com/ethpandaops/ethereum-package/src/cl/lighthouse/lighthouse_launcher.star[82:38]:
  add_service(name="cl-1-lighthouse-geth", config=ServiceConfig(image="ethpandaops/lighthouse:stable", ports={"http": PortSpec(number=4000, transport_protocol="TCP", application_protocol="http"), "metrics": PortSpec(number=5054, transport_protocol="TCP", application_protocol="http"), "tcp-discovery": PortSpec(number=9000, transport_protocol="TCP", application_protocol=""), "udp-discovery": PortSpec(number=9000, transport_protocol="UDP", application_protocol="")}, public_ports={}, files={"/jwt": "jwt_file", "/network-configs": "el_cl_genesis_data"}, cmd=["lighthouse", "beacon_node", "--debug-level=info", "--datadir=/data/lighthouse/beacon-data", "--disable-enr-auto-update", "--enr-address=KURTOSIS_IP_ADDR_PLACEHOLDER", "--enr-udp-port=9000", "--enr-tcp-port=9000", "--listen-address=0.0.0.0", "--port=9000", "--http", "--http-address=0.0.0.0", "--http-port=4000", "--slots-per-restore-point=32", "--disable-packet-filter", "--execution-endpoints=http://{{kurtosis:ae65c71a46a54a71b74fb2ce26e9f5d7:ip_address.runtime_value}}:8551", "--jwt-secrets=/jwt/jwtsecret", "--suggested-fee-recipient=0x8943545177806ED17B9F23F0a21ee5948eCaa776", "--metrics", "--metrics-address=0.0.0.0", "--metrics-allow-origin=*", "--metrics-port=5054", "--enable-private-discovery", "--testnet-dir=/network-configs"], env_vars={"RUST_BACKTRACE": "full"}, private_ip_address_placeholder="KURTOSIS_IP_ADDR_PLACEHOLDER", ready_conditions=ReadyCondition(recipe=GetHttpRequestRecipe(port_id="http", endpoint="/eth/v1/node/health"), field="code", assertion="IN", target_value=[200, 206], timeout="15m"), labels={"ethereum-package.client": "lighthouse", "ethereum-package.client-image": "ethpandaops-lighthouse_stable", "ethereum-package.client-type": "beacon", "ethereum-package.connected-client": "geth", "ethereum-package.sha256": ""}, tolerations=[], node_selectors={}))
  Caused by: Unexpected error occurred starting service 'cl-1-lighthouse-geth'
  Caused by: An error occurred waiting for all TCP and UDP ports to be open for service 'cl-1-lighthouse-geth' with private IP '172.16.0.11'; this is usually due to a misconfiguration in the service itself, so here are the logs:
  == SERVICE 'cl-1-lighthouse-geth' LOGS ===================================
  Feb 21 17:13:47.379 INFO Logging to file                         path: "/data/lighthouse/beacon-data/beacon/logs/beacon.log"
  Feb 21 17:13:47.381 INFO Lighthouse started                      version: Lighthouse/v6.0.1-bf955c7
  Feb 21 17:13:47.381 INFO Configured for network                  name: custom (/network-configs)
  Feb 21 17:13:47.394 INFO Data directory initialised              datadir: /data/lighthouse/beacon-data
  Feb 21 17:13:47.394 WARN Discv5 packet filter is disabled
  Feb 21 17:13:47.402 WARN The slots-per-restore-point flag is deprecated
  Feb 21 17:13:47.402 INFO Deposit contract                        address: 0x4242424242424242424242424242424242424242, deploy_block: 0
  Feb 21 17:13:47.436 INFO Blob DB initialized                     oldest_data_column_slot: None, oldest_blob_slot: Some(Slot(0)), path: "/data/lighthouse/beacon-data/beacon/blobs_db", service: freezer_db
  Feb 21 17:13:52.524 INFO Starting from known genesis state       service: beacon
  Feb 21 17:13:52.529 INFO Block production enabled                method: json rpc via http, endpoint: Auth { endpoint: "http://172.16.0.10:8551/", jwt_path: "/jwt/jwtsecret", jwt_id: None, jwt_version: None }
  Feb 21 17:13:52.551 CRIT Failed to start beacon node             reason: Failed to build beacon chain: Head block not found in store
  Feb 21 17:13:52.551 INFO Internal shutdown received              reason: Failed to start beacon node
  Feb 21 17:13:52.551 INFO Shutting down..                         reason: Failure("Failed to start beacon node")
  Failed to start beacon node

  == FINISHED SERVICE 'cl-1-lighthouse-geth' LOGS ===================================
  Caused by: An error occurred while waiting for all TCP and UDP ports to be open
  Caused by: Unsuccessful ports check for IP '172.16.0.11' and port spec '{privatePortSpec:0xc0005ef8f0}', even after '240' retries with '500' milliseconds in between retries. Timeout '2m0s' has been reached
  Caused by: An error occurred while calling network address '172.16.0.11:5054' with port protocol 'TCP' and using time out '200ms'
  Caused by: dial tcp 172.16.0.11:5054: i/o timeout

[jsvisa]

I'll pick up this issue, and send the fix PR later