We’re excited to announce the release of Zebra 3.0.0—the most feature-rich Zebra release ever! 
In addition to supporting NU6.1, the latest network upgrade, we’ve also focused on making Zebra easier to run in production, faster to sync, and available on more platforms. 
A detailed overview is available here.
Congrats! A quick flag: it looks like Zebra’s ARM builds are not pushed to Docker Hub yet, so the example in the release post is throwing an error on ARM platforms:
% docker pull zfnd/zebra:latest
Error response from daemon: no matching manifest for linux/arm64/v8 in the manifest list entries: no match for platform in manifest: not found
I’ll have a look at this one. Thank you for reporting!
Really excited to try the native ARM release on my Rock 5B that currently runs an ethereum node
+1 on this. I tried to update my node this morning and got an error
no matching manifest for linux/arm64/v8 in the manifest list entries
I have nowhere near the skills required to audit this piece of art, but somehow it’s still easy to tell it’s top notch quality. Thanks a lot for all the work that must have gone behind this. Consider using the dev fund, it’s really made for those kind of contributions to the ecosystem.
Two questions:
Thanks again!!
Hi!
No, prometheus alert are not yet ready. We collect prometheus metrics but we have not yet come up with a set of rules for alerting. This is something that we want to do and still needs to be prioritised.
Before we do that, we need to better understand zebra’s baseline performance so that we know when we are deviating from it both in order to identify regressions and for node operators to know when there may be something wrong with their node. If you are interested in reading more about this work to analyse, instrument, and improve the performance of Zebra, it is collected under the Stampede milestone on Github.
I’m not sure what you mean by the terminal graphical interface to Zebra since we’ve never had a way to interact with zebra via the terminal and have no plans to work on that in future 
If you’re referring to the progress bar feature, this was something that we developed a while back as part of what we call a “hack sprint” where developers are free to work on something that they want to implement or experiment with which may not be a priority or something that is in our backlog. This work is normally hidden behind feature flags in Zebra while we gauge interest from users.
The other reason this is not a default setting is because, when enabled, logs would go to a file instead of being displayed on the terminal. Although we have no specific plans to develop this further, we are always happy to receive feedback to improve Zebra’s usability.
I hope that helps! Happy to answer any follow up questions or clarify further.
Makes perfect sense indeed! Feel free to release it a bit before it feels completely polished, it’s possible the community may have useful feedback for you.
Sorry for not being clear, yes indeed.
It was sorta super cute to see it as part of my tmux terminals, but other than that no particular use for it. Maybe it’s time I just run this as a service now that it’s production level quality. I do not see that in your documentation though. I could create the service file myself, but out of curiosity, are you planning to document such option later on?
We do! Here it is:
And yes, we should document this better 
Hey guys, I’m not sure if this is the right place to ask, but what happened to the lockbox?
It only has 507 $ZEC in it now.
Is this a Zebrad glitch? Was $ZEC withdrawn from it to pay the retroactive grants, or was it stolen? 
edit
Sorry for the false alarm, looks like everything is actually normal
So, what is the situation about the arm64 docker image?
As many of you already saw here:
I’m playing with raspberry pi + zebrad, I had to compile a docker image and use my own dockerhub repository.
I don’t want to release a RPi image using my repo, it should always use the official versions.
Hi!
We’re planning another release shortly and hope to be able to release the arm64 docker image at the same time..
For reference there was a one-time lockbox disbursement for an address that will be managed by the retroactive grants program, as specified in ZIP 271: Dev Fund Extension and One-Time Disbursement and approved in multiple polls (ZCAP, ZAC and coin holder)
We have just released Zebra 3.1.0 and published both amd64 and arm64 images to docker hub: zfnd/zebra - Docker Image
Thank you, I can confirm docker was able to pull and run the image (Zebra 3.1.0) on Raspberry Pi.
(@emersonian note that the current config from the workshop does not work out of the box, something to do with the way config/env is addressed, I’m not sure what ended up fixing mine but basically moved the listing config to the docker compose to make it work.
```
environment:
- ZEBRA_NETWORK__NETWORK=Mainnet
- ZEBRA_STATE__CACHE_DIR=/var/cache/zebrad-cache
- ZEBRA_RPC__LISTEN_ADDR=0.0.0.0:8232
- ZEBRA_RPC__ENABLE_COOKIE_AUTH=false
```
Be aware of the breaking changes documented in 3.0.0-rc.0: Release Zebra 3.0.0-rc.0 · ZcashFoundation/zebra · GitHub