[Node Operator Question] Node not syncing with docker #287
Replies: 5 comments 5 replies
-
One possibility is that Docker might be inhibiting communication to the localhost. Please check to ensure there are no issues with your Docker settings. |
Beta Was this translation helpful? Give feedback.
-
Waiting for Bedrock node to initialize... check bedrock-init container logs |
Beta Was this translation helpful? Give feedback.
-
Here I am, trying again with this conf: .env:
op-geth is stuck like this for a while:
and the l2 rpc shows block
Logs for each container attached below. |
Beta Was this translation helpful? Give feedback.
-
Solved by setting up an http proxy listening on |
Beta Was this translation helpful? Give feedback.
-
You need to use host.docker.internal instead of 127.0.0.1 because 127.0.0.1 means localhost in the container (Not the host) Sorry for the late response. This should be documented |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Are you running the most up to date node software?
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
Hello, I am trying to set up a mainnet optimism node with docker. Here's what I did:
Then edited .env like this:
Then:
But it never synces. I noticed there are some error in the logs. I will attach the op-node and op-geth error logs here.
In particular, the errors seems to be:
But I am sure the L1 node is reachable on that port:
Protocol Description
v1.101308.2
v1.7.0
mainnet/op
10
1
Node Logs
op_node.log
op_geth.log
Additional Information
No response
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions