IA1.2.4 Generate dockers for the l1, dev node, OP Geth, and OP node services by shenkeyao · Pull Request #182 · EspressoSystems/optimism-espresso-integration

shenkeyao · 2025-06-20T23:18:32Z

Closes https://app.asana.com/1/1208976916964769/project/1209392461754458/task/1210546932882749?focus=true.

This PR:

Create a Dockerfile for the L1 Geth service, including the geth installation command for different architectures.
Create a Dockerfile for the OP Geth service.
Create a Dockerfile for the OP node (for the sequencer, the verifier, and the Caff node), the batcher, and the proposer services.
Add an op-geth-init service to avoid manual initialization with the genesis file.
Remove instruction from README that's no longer applicable.

This PR does not:

Fix the Caff node, the batcher, and the proposer services, which are dependent on the contract deployment fix.

How to test this PR:

docker compose up --build -d to build.
docker compose logs -f to run all services and check that the L1 Geth, the Espresso dev node, the OP Geth, the OP node sequencer, and the OP node verifier work.
For more instructions, see the Docker Compose section in README_ESPRESSO.md.

shenkeyao · 2025-06-20T23:21:56Z

espresso/dockerfiles/op-stack/Dockerfile

@@ -0,0 +1,112 @@
+# OP Stack Dockerfile, simplified from ops/docker/op-stack-go/Dockerfile


@Ancient123 Following the pattern in op-stack-go/Dockerfile, I used this file for the OP node, batcher, and proposer, instead of creating one Dockerfile for one service--is this okay?

This is fine.

espresso/dockerfiles/op-stack/Dockerfile

philippecamacho · 2025-06-23T16:16:14Z

Will the other services (Espresso node, Caff node) be implemented in another PR?

philippecamacho · 2025-06-23T16:17:50Z

espresso/dockerfiles/l1-geth/Dockerfile

+    mv "$GETH_DIR/geth" /usr/local/bin/geth && \
+    rm -rf geth.tar.gz "$GETH_DIR" && \
+    chmod +x /usr/local/bin/geth
+


We should check the hash GETH_SHA here.

Oh, we do! It's located around 10+ lines above, the command starting from GETH_SHA=.

Right, but this variable GETH_SHA does not seem to be used anywhere? Should not we compute the hash of the tar.gz file against GETH_SHA or something similar?

Fixed in 5559716, with a sha256sum check.

philippecamacho · 2025-06-23T16:19:00Z

espresso/dockerfiles/op-stack/Dockerfile

+
+# Rust builder for Espresso crypto libraries
+FROM --platform=$BUILDPLATFORM rust:1.84.1-alpine3.20 AS rust-builder
+ARG ESPRESSO_NETWORK_GO_VER=0.0.34


Add a TODO to check the hash of the espresso go library when we switch to the new one. cc @dailinsubjam

TODO added: ce1dc2c. Also added an Asana task.

shenkeyao · 2025-06-23T16:35:10Z

espresso/docker-compose.yml

+      context: ./dockerfiles/l1-geth
    image: l1-geth:espresso
    volumes:
      - ../config/l1-genesis-devnet.json:/l1-genesis-devnet.json:ro


Pasting @Ancient123's comment from Slack:

when doing mounts at runtime don't mount individual files. If the file gets rewritten on the host machine, it won't take affect on the docker, because it can hold onto an older handle for the previous file.

philippecamacho · 2025-06-23T16:38:13Z

leloup@leloup-Legion-7-16ITHg6:~/repositories/espressosys/optimism-espresso-integration/espresso$ docker compose logs -f | grep op-batcher
op-batcher-1         | t=2025-06-23T16:31:59+0000 lvl=info msg="Initializing Batch Submitter"
op-batcher-1         | t=2025-06-23T16:31:59+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:01+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:03+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:05+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:07+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:09+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:11+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:13+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:15+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:17+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:19+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:21+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:23+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:25+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:27+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:29+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:31+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:33+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:35+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:37+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:39+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:41+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:43+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:45+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:47+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:49+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:51+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:53+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:55+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:57+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:57+0000 lvl=info msg="Stopping batcher"
op-batcher-1         | t=2025-06-23T16:32:57+0000 lvl=info msg="Batch Submitter stopped"
op-batcher-1         | t=2025-06-23T16:32:57+0000 lvl=crit msg="Application failed" message="failed to setup: failed to build static L2 endpoint provider: operation failed permanently after 30 attempts: address unavailable (http://op-node-sequencer:8545)"

Is this expected?

shenkeyao · 2025-06-23T16:45:34Z

Will the other services (Espresso node, Caff node) be implemented in another PR?

@philippecamacho The Espresso dev node uses the Espresso pre-built image, so it doesn't need a Dockerfile. The Caff node uses the same target as the OP node does, so we don't need to specify a Dockerfile for it separately.

shenkeyao · 2025-06-23T16:46:31Z

leloup@leloup-Legion-7-16ITHg6:~/repositories/espressosys/optimism-espresso-integration/espresso$ docker compose logs -f | grep op-batcher
op-batcher-1         | t=2025-06-23T16:31:59+0000 lvl=info msg="Initializing Batch Submitter"
op-batcher-1         | t=2025-06-23T16:31:59+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:01+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:03+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:05+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:07+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:09+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:11+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:13+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:15+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:17+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:19+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:21+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:23+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:25+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:27+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:29+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:31+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:33+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:35+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:37+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:39+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:41+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:43+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:45+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:47+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:49+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:51+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:53+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:55+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:57+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:57+0000 lvl=info msg="Stopping batcher"
op-batcher-1         | t=2025-06-23T16:32:57+0000 lvl=info msg="Batch Submitter stopped"
op-batcher-1         | t=2025-06-23T16:32:57+0000 lvl=crit msg="Application failed" message="failed to setup: failed to build static L2 endpoint provider: operation failed permanently after 30 attempts: address unavailable (http://op-node-sequencer:8545)"

Is this expected?

@philippecamacho Not expected! I'll investigate this.

shenkeyao · 2025-06-24T00:16:43Z

leloup@leloup-Legion-7-16ITHg6:~/repositories/espressosys/optimism-espresso-integration/espresso$ docker compose logs -f | grep op-batcher
op-batcher-1         | t=2025-06-23T16:31:59+0000 lvl=info msg="Initializing Batch Submitter"
op-batcher-1         | t=2025-06-23T16:31:59+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:01+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:03+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:05+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:07+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:09+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:11+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:13+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:15+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:17+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:19+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:21+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:23+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:25+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:27+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:29+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:31+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:33+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:35+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:37+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:39+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:41+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:43+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:45+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:47+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:49+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:51+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:53+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:55+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:57+0000 lvl=warn msg="failed to dial address, but may connect later" addr=http://op-node-sequencer:8545
op-batcher-1         | t=2025-06-23T16:32:57+0000 lvl=info msg="Stopping batcher"
op-batcher-1         | t=2025-06-23T16:32:57+0000 lvl=info msg="Batch Submitter stopped"
op-batcher-1         | t=2025-06-23T16:32:57+0000 lvl=crit msg="Application failed" message="failed to setup: failed to build static L2 endpoint provider: operation failed permanently after 30 attempts: address unavailable (http://op-node-sequencer:8545)"

Is this expected?

@philippecamacho Not expected! I'll investigate this.

Made a separate task for this issue because it also occurred on the default branch: https://app.asana.com/1/1208976916964769/project/1209392461754458/task/1210618856384949?focus=true. Will fix it in a separate PR.

espresso/docker-compose.yml

jparr721

Volumes will all need to be deployed in EFS, heads up that that's decidedly nontrivial. We can talk about that.

jparr721 · 2025-06-25T15:41:48Z

espresso/docker-compose.yml

+      - op-geth-data:/data
+    entrypoint: ""
+    command: >
+      sh -c "


This might be really annoying in terraform. I'd recommend checking how arbitrary scripts work in there. Ideally we'd just make this part of the container instead, so we can fork their container and then add this as a setup step (I think).

~~In the terraform I created in the tee-op-deploy repo, I added commands like this to the container definition. Can we keep them here till the terraform PR (not sent yet) is merged?~~

Update: I moved these commands to l1-geth-init.sh and op-geth-init.sh scripts.

…rvice

shenkeyao · 2025-07-10T19:41:11Z

Volumes will all need to be deployed in EFS, heads up that that's decidedly nontrivial. We can talk about that.

Thanks @jparr721. As discussed on this Slack thread, we are not going to use EFS for the devnet.

shenkeyao · 2025-07-10T19:45:22Z

Services in the PR title are working now. Will have another PR for the remaining services that depend on the contract deployment.

dailinsubjam

LGTM. L1 Geth, the Espresso dev node, the OP Geth, the OP node sequencer, and the OP node verifier work for me.

…ervices (#182) * Fix services except the nonce * Simpify manual work * Save fixes WIP * Revert dockerfile change * Save parameter fixes * Add fixes * All services running again. * Fix timestamp and increase dev period * Install pnpm with nix. * More cleanups * Revert go.mod, fix install syntax, add const env, add more comments * Add env file * Fix after merge * Add changes for l1 terraform * Update for op-geth * Fix op node related docker * Add SHA check * Add a TODO * Add jwt back * Create GH actions workflow * Fix tag * Fix path and tag * Add init scripts * Fix paths and settings after adding init scripts * Fix path for CI workflow * Move files * Reorder commands * Fix path * More path update --------- Co-authored-by: Philippe Camacho <philippe@espressosys.com>

shenkeyao added 2 commits June 20, 2025 15:36

Fix services except the nonce

31cc442

Simpify manual work

86c1f21

shenkeyao requested review from Ancient123, QuentinI, dailinsubjam and philippecamacho June 20, 2025 23:18

shenkeyao commented Jun 20, 2025

View reviewed changes

philippecamacho reviewed Jun 23, 2025

View reviewed changes

espresso/dockerfiles/op-stack/Dockerfile Show resolved Hide resolved

philippecamacho reviewed Jun 23, 2025

View reviewed changes

shenkeyao commented Jun 23, 2025

View reviewed changes

shenkeyao added 2 commits June 23, 2025 15:01

Save fixes WIP

5b68476

Revert dockerfile change

3b09bd8

dailinsubjam reviewed Jun 24, 2025

View reviewed changes

espresso/docker-compose.yml Outdated Show resolved Hide resolved

Save parameter fixes

62364ab

jparr721 reviewed Jun 25, 2025

View reviewed changes

shenkeyao and others added 9 commits June 25, 2025 13:09

Add fixes

3ffab24

All services running again.

8e27ee6

Fix timestamp and increase dev period

4606b0b

Install pnpm with nix.

88843cf

More cleanups

6b000d3

Merge branch 'celo-integration-rebase-13.1' into keyao/fix-op-node-se…

b11a5ee

…rvice

Revert go.mod, fix install syntax, add const env, add more comments

1fa8a89

Add env file

033d6c6

Merge branch 'keyao/fix-op-node-service' into keyao/docker-service

32ae00e

shenkeyao changed the title ~~IA1.2 Generate dockers for services~~ IA1.2.4 Generate dockers for the l1, dev node, OP Geth, and OP node services Jul 10, 2025

shenkeyao added 3 commits July 10, 2025 12:20

Merge branch 'celo-integration-rebase-13.1' into keyao/docker-service

8132c1b

Add SHA check

5559716

Add a TODO

ce1dc2c

shenkeyao added 11 commits July 10, 2025 14:45

Add jwt back

9711ffe

Create GH actions workflow

f213ffa

Fix tag

1b38e99

Fix path and tag

f409b11

Add init scripts

5d5f4d2

Fix paths and settings after adding init scripts

e753857

Fix path for CI workflow

2bff8f1

Move files

fe7a26b

Reorder commands

e76808c

Fix path

6d0c27b

More path update

13d42dd

dailinsubjam approved these changes Jul 16, 2025

View reviewed changes

shenkeyao merged commit 6905e3f into celo-integration-rebase-13.1 Jul 18, 2025
32 checks passed

shenkeyao deleted the keyao/docker-service branch July 18, 2025 17:55

		@@ -0,0 +1,112 @@
		# OP Stack Dockerfile, simplified from ops/docker/op-stack-go/Dockerfile

Conversation

shenkeyao commented Jun 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

This PR:

This PR does not:

How to test this PR:

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

philippecamacho commented Jun 23, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

philippecamacho commented Jun 23, 2025

Uh oh!

shenkeyao commented Jun 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

shenkeyao commented Jun 23, 2025

Uh oh!

shenkeyao commented Jun 24, 2025

Uh oh!

Uh oh!

jparr721 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shenkeyao Jul 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shenkeyao commented Jul 10, 2025

Uh oh!

shenkeyao commented Jul 10, 2025

Uh oh!

dailinsubjam left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

shenkeyao commented Jun 20, 2025 •

edited

Loading

shenkeyao commented Jun 23, 2025 •

edited

Loading

shenkeyao Jul 10, 2025 •

edited

Loading