-
Notifications
You must be signed in to change notification settings - Fork 19
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
Missing dependency for .zarr
files
#77
Comments
The blosc library is not installed. This is a server dependency. Are you using omero-server-docker? or another server. |
Hi @jburel , thanks for the quick reply. I have essentially used the docker-example-omero which led to the error. |
Thanks. |
This issue has been mentioned on Image.sc Forum. There might be relevant details there: https://forum.image.sc/t/images-batch-import-into-a-dataset-in-omero-using-ezomero-2-1-0/89529/22 |
Thanks for the lightning-fast fix @jburel . How often are docker containers released? I.e., how long would it take for this change to take effect in production? |
@jo-mueller please see https://hub.docker.com/r/openmicroscopy/omero-server/tags for the de-facto release frequency. In short, it is a manual process, so please bear with us, thank you :) |
Will keep my eyes peeled then :) Your work is very appreciated, thanks! |
@jo-mueller A new version of the omero-server-docker has been pushed to dockerhub. It should include |
Thanks big time! 👍 |
Hi all,
following up some discussions on image.sc about the upload and use of .zarr files to OMERO, I have also discovered, that the problem in the latter of those issues (
blosc
dependency missing for "proper" zarr usage) persists in the container-based setup.Error I observed
I uploaded a ZARR file to our OMERO instance as discussed in this thread and the image cannot be displayed there.
When I download (parts of) the image via
ezomero
like this:I receive the following error:
Possible solution
As discussed in this image-sc thread, the problem is likely just a missing dependency (e.g.,
libblosc
). To fix it, I could probably simply build my own container based on the omero containers and fix it, but including the dependency here would probably be the more sustainable solution.I would be happy to send a PR to fix it if you can point me to the correct place where to add it. That being said, I am not sure whether this is a missing dependency of the webserver or the other involved containers.
The text was updated successfully, but these errors were encountered: