-
Notifications
You must be signed in to change notification settings - Fork 109
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
Not able to build zeta-chain node #3316
Comments
https://github.com/zeta-chain/zetacored-docker is our actively supported way of running zetacored in docker. I can fix this up if you really need it. What do you use to automate the upgrades? |
This would be much needed for us, so our nodes can run. We don't use anything to automate upgrade unfortunately. zetacored-docker is not working for us since it's wiping disk and downloading full node snapshot and we run archive nodes. |
You set |
But it would still download snapshot every time, right? And for archive node it's 5Tb. |
If the snapshot restore completes it will not be restored again so long as you have a persistent volume mounted on I did attempt to test archive snapshot restore yesterday. It did end up failing around ~1TB, I think there are some issues with cloudflare and range headers. |
Cool, we'll try this out. But is there a change you can provide image earlier on the dockerhub so we have nodes running until we switch to zetacored-docker? |
Describe the Bug
When I run
docker build . -f Dockerfile
It's expected for image to be built.
Building on macOS Sonoma Version 14.5
p.s. It's the same issue from your github action - https://github.com/zeta-chain/node/actions/runs/12237577778/job/34133645670
The text was updated successfully, but these errors were encountered: