WARN: The "L1_RPC_URL" variable is not set. Defaulting to a blank string.

[junha-ahn]

I run from node this link (https://docs.manta.network/docs/manta-pacific/Replica%20Node)

And I think it use op-stack.

$ docker-compose logs --tail 10 -f
WARN[0000] The "L1_RPC_URL" variable is not set. Defaulting to a blank string.
celestia-light-node      | 2024-02-15T01:46:09.422Z	INFO	header/store	store/store.go:365	new head	{"height": 785882, "hash": "14B957FA80BED452B824F1EB1764528AFF2FC908029DDE3FD84B70A6028FF84A"}

docker-compose.yaml

...
celestia:
   ...
op-geth:
   ... 
op-node:
    image: ".../op-node:celestia-3.0.0"
    stop_signal: SIGINT
    stop_grace_period: 30s
    command: >
      op-node
      --l1="${L1_RPC_URL}"
      --l2=http://l2:8551
      --l2.jwt-secret=/config/test-jwt-secret.txt 
      ...

$ docker inspect {op-node-container-id}
[
  { 
     "ID": "...",
     "Args": [
        "--l1=https://my-ethereum-rpc-url",
      ]
  }
]

so I think, I put l1 links well, but it prints "The "L1_RPC_URL" variable is not set..."

I dont understand why it prints, and which container(op-geth,op-node,celestia) prints it

• How can I check up currently connected L1_RPC peer? I cant find it here(https://docs.optimism.io/builders/node-operators/json-rpc#op-node)

$ op-node
error "flag l1 is reuiqred"

• It seems like the op-node has set up l1_rpc correctly based on the above context. (An error occurs immediately if you run it without l1 option.)