Reth execution client reports of invalid JWT at init

[sameersubudhi]

Expected behavior

The execution clients shouldn't report any issues and should work normally.

Actual behavior

Running a Lisk node with op-reth execution client reports of Invalid JWT error at init but only once, as seen in the logs below.
The node however functions normally, syncs with the L2 network and reports no more issues later.

sameer@Sameers-MBP lisk-node % docker logs -f lisk-node-execution-1                                                 

------------------------------------------------------------------------------------------------------------
Starting op-reth execution node under '/data'...
------------------------------------------------------------------------------------------------------------

ts=2024-07-24T12:37:16.369169668Z level=info target=reth::cli message="Initialized tracing, debug log directory: /root/.cache/reth/logs/4202"
ts=2024-07-24T12:37:16.392493793Z level=info target=reth::cli message="Starting reth" version="\"1.0.3 (390f30aa)\""
...
...
ts=2024-07-24T12:37:21.429181337Z level=error target=engine::jwt-validator message="Invalid JWT: Authorization header is missing or invalid"
...

Steps to reproduce

CLIENT=reth docker compose up --build --detach

Which version(s) does this affect? (Environment, OS, etc...)

PR #27 (branch: 24-unable-to-build-reth-images, commit: 2166361)

Additional Information

Both the op-node and the execution (op-reth in this case) client already share the same JWT token and the container has everything set properly for the jwtsecret (--authrpc.jwtsecret) to be used by the reth client.

[0xChupaCabra]

manually added --l2.jwt-secret=/jwt.hex and --authrpc.jwtsecret=/jwt.hex to both entrypoints, mounted ./jwt.hex:/jwt.hex as volumes in docker-compose.yml , then booted op-node first, later reth and it worked