Dev node does not propagate L1 => L2 actions if L1 is a forked mainnet

[vasapower]

Describe the bug Running the complete development environment (by following this guide) works well only if the L1 network is freshly new (using hardhat/ganache). However, if the L1 chain is forked, all the L1 => L2 communications are not propagated (e.g. no 5000 ETH to test accounts) and it's impossible to submit transactions to L2.

To Reproduce Steps to reproduce the behavior:

1. Obtain all the Optimism Development Environment Docker images (as explained here)
2. Edit the l1_chain image to let it be able to fork the mainnet (e.g. by applying this fix to the original hardat image) to let it allow to correctly fork mainnet
3. Rebuild the image through the command docker-compose build l1_chain
4. Fork mainnet by inserting your node link in the optimism/ops/envs/l1_chain.env file
5. Run the containers through the command docker-compose up and wait for the startup to be completed
6. The balance of all the 20 test addresses is always 0 on l2

Expected behavior The environment should work like with a brand new L1 chain but the behavior is that L1 transactions are not propagated to L2 (blockNumber on L2 should be greater or equal to 20 due to the transfer of ETHs to the 20 test addresses but it is always 0, even after hours)

Screenshots No screenshots available

System Specs:

• OS: Docker
• Package Version (or commit hash): branch develop, commit c0c5af0b2c66ac0a440c10a3e9f2fd42f0ebc116

Additional context No other info

Many thanks!