-
Notifications
You must be signed in to change notification settings - Fork 193
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
feat: publish chaosnet image #1218
Conversation
file: contrib/docker/chaosnet.Dockerfile | ||
context: . | ||
push: true | ||
platforms: linux/amd64,linux/arm64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@NibiruHeisenberg Could you confirm that this would be ok?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this will work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would name the tag ghcr.io/nibiruchain/nibiru:genesis
or something similar to indicate that it has the same binary as ghcr.io/nibiruchain/nibiru, but with genesis files included.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can I access a specific tag if this? Nibiru:genesis:v0.19?
Description
Publish a chaosnet image when we tag a new release. This image has a localnet configured to run properly
Purpose
This can be pulled to run quickly a new chain without having to build it again