-
Notifications
You must be signed in to change notification settings - Fork 9
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
Error running update #21
Comments
Hi @BioinfoTongLI, thanks for the heads up. What happens if you build the image locally? Does the issue go away? If so, happy to release a new version ASAP. All the best, |
Hi @joshmoore, I just ran local docker build in
However the
It seems that a new version would be great! Best, |
Kicking off the build process. (Already thinking about a Github action...) |
This issue has been mentioned on Image.sc Forum. There might be relevant details there: https://forum.image.sc/t/fiji-fails-to-launch-after-update/44582/8 |
I'm see the same error trying to build. Posted to image.sc. |
Ok, will follow that up - Sorry, not used to report everything on image.sc yet, will do that in the future. |
Cross-posting is fine! No worries.
This is because a Fiji plugin, I'm removing it from the update site for now. |
Thanks, @hinerm ! ❤️ |
@hinerm, it may be unrelated then (or a secondary issue?): Trying to build a new image I still see:
like #21 (comment) and trying to build @BioinfoTongLI's Dockerfile:
I see:
as in the description. |
@hinerm as a new year follow-up, any ideas on next steps here? |
I believe this is due to some drift in the older Fiji that is living in the
How are you building the new image? Starting from the current But not sure how you got to your |
Using the make file:
If I add a
|
8 is still failing. I'm going to try bumping to 11+. |
Any update on this? I'm seeing different outputs in a script I'm running locally vs on the openjdk-8 Docker, so I wanted to update, and am running into the same issue. Thanks guys, appreciate the help!
|
(FWIW, if I don't try to build my own Fiji Docker from scratch, but just try to do
I do get a slightly different stack trace after all the downloading - I've tried with and without the
|
As a workaround, I made the world's dumbest Dockerfile to just get Fiji installed, you can grab it at https://hub.docker.com/r/bethcimini/simplefiji/tags, full Dockerfile below. It's obviously not a replacement for the real thing, but I can confirm it's currently executing my script, so hopefully it can serve as a patch for others.
|
Hi @bethac07. Sorry for not reporting back. My attempts to get openjdk11 working failed: https://github.com/fiji/dockerfiles/compare/openjdk11?expand=1 With the Java-8 update site, I see the GUI service error above. If I try to remove it:
then there are issues when updating the other update sites to https. Personally, your Dockerfile doesn't look dumb at all. I think the critical difference, though, is that the ones in this repo attempt to update while yours doesn't. If that's the strategy we want to adopt, I can open a PR. |
I have a strong suspicion that's it as well, though TBH I didn't test that out once I got something I could actually use to run what I needed last night ;) . The other (not mutually exclusive of course) option is just that whatever OS the openjdk8 docker you guys are currently It also lacks some of the nice things you guys have with the entrypoint script, and setting up various security policies etc, so likely you'd want to add all of those back in, but since for my purposes I literally just need a Docker with Fiji in it so that I can I leave it to you guys to decide if you want to change implementation strategies, but glad this may have been helpful! |
@hinerm: coming back to this due to the recent ping to the image.sc thread -- any ideas? Would a brainstorming help? |
Situation persists. |
Sorry to hear of all the problems. It's all because https://downloads.imagej.net/fiji/latest still points to However, since the P.S. Some clarifying points in response to above discussion:
Both of these points led me to think that the Dockerfile must not be pulling in a recent-enough Fiji bundle, which is how I noticed/remembered about the |
I have now:
@joshmoore Please try rebuilding the Docker image again and see whether problems persist. |
This issue has been mentioned on Image.sc Forum. There might be relevant details there: https://forum.image.sc/t/fiji-bundles-updated-with-newest-zulu-8-jdk-fx/65809/1 |
Situation de-persists:
🎉 🎈 🎊 I'll run the rest of the builds now and get them up on Docker Hub. (I'll also go back to my attempt at OpenJDK 11) |
New tags pushed: https://hub.docker.com/r/fiji/fiji/tags (Note: sadly all the older tags have been removed due to Docker Hub policy changes) |
Hello,
I am getting an error with both tag
latest
andfiji-openjdk-8
Here is my
Dockerfile
The last action throws this error:
Any thoughts?
Cheers!
Tong
The text was updated successfully, but these errors were encountered: