Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue when launching new default cluster #168

Open
vcastellm opened this issue Feb 12, 2025 · 5 comments
Open

Issue when launching new default cluster #168

vcastellm opened this issue Feb 12, 2025 · 5 comments

Comments

@vcastellm
Copy link

When running a new enclave:

kurtosis run github.com/ethpandaops/optimism-package --args-file https://raw.githubusercontent.com/ethpandaops/optimism-package/main/network_params.yaml --enclave op

It worked some days ago, today it's constantly failing with the error:

"Application failed" message="failed to setup: unable to create the rollup node config: failed to decode rollup config: json: unknown fiel d \"chain_op_config\"

Looks like an update to the CL image?

@jhkimqd
Copy link

jhkimqd commented Feb 13, 2025

@vcastellm we saw this issue as well a few days back and it seemed to happen after the develop tag of the op-node got updated. An immediate workaround that is working is to replace the op-node image with a tag that was released after this issue - which seems to fix it.
https://github.com/ethpandaops/optimism-package/blob/main/src/package_io/input_parser.star#L16

 DEFAULT_CL_IMAGES = {
-    "op-node": "us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:develop",
+    "op-node": "us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.11.0-rc.2",
     "hildr": "ghcr.io/optimism-java/hildr:latest",
 }

At the time of this post, it seems like the develop tag got updated again, and it seems to work after updating the image with docker pull us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:develop

Image

@vcastellm
Copy link
Author

It would be better to pin the image to a specific version, wdyt?

@vcastellm
Copy link
Author

My workaround at this moment is running using an specific commit from this repo:

kurtosis run github.com/ethpandaops/optimism-package@c32a626c575983331c1d4fc52c507588e385ed56 --args-file https://raw.githubusercontent.com/ethpandaops/optimism-package//c32a626c575983331c1d4fc52c507588e385ed56/network_params.yaml --enclave op

@jhkimqd
Copy link

jhkimqd commented Feb 13, 2025

It would be better to pin the image to a specific version, wdyt?

In Kurtosis CDK, we've pinned it to v1.11.0-rc.2

@vcastellm
Copy link
Author

Pinning the correct combination of images fixes the kurtosis setup, use this as reference https://gist.github.com/vcastellm/43d9c74c752435c934114841e1039cc2

oneliner:

curl -O https://gist.githubusercontent.com/vcastellm/43d9c74c752435c934114841e1039cc2/raw/134ce5b160971281327f410002650e8d3f5d7009/kurtosis-op-stack.yaml
kurtosis run github.com/ethpandaops/optimism-package --args-file kurtosis-op-stack.yaml --enclave op

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants