Closed danielFlemstrom closed 1 year ago
This is weird, doesn't look like it should be docker related. It basically says it can't access the GeoTiff file, which can have a couple of reasons:
I'm not a Docker user myself and the Docker image is maintained by @mmacata so I can't really look into the issue.
Does it work in the most recent deployed version at editor.openeo.org?
Yes and all check-ins after that version. So with a bit of luck, re-generating the :latest would fix it. I used the same EO-Server and the same process tree to test.
Hi @danielFlemstrom, the latest
tag is updated for every release which was v0.11.0
~ six month ago. So the same error should appear for mundialis/openeo-web-editor:v0.11.0
and should already have been there this long.
So to be sure what's inside, it might makes sense to pin version either to a commit hash or to a released version.
OK, my bad. I assumed latest was the automatic build of the latest commit, or at least labelled commit. Maybe tag the "latest"s corresponding commit with latest would help as well ? Anyway it seems all after 0.11.4 works fine when i pulled using the commit hash. @mmacata just say if you want me to test anything!
The issue you are seeing is likely fixed by #267. And it's probably time for a 0.12.0 release :)
We pass the decision to what latest should be to a github action called docker/metadata-action and simply use the default behaviour of it.
So I also think that it would be time for a new release (:
Fixed the remaining bugs for 0.12.0 and released it. The container should be updated in some minutes.
mundialis/openeo-web-editor:latest
generates an error for the process (pseudo form) loadcollection->save (geotiff)None of the available hashes between the one used in
https://editor.openeo.org
(0.11.4) and 78257122a486ca19ca46c1944432d9d9afa0532c gives that error so i am not sure why:latest
complains..Is there a way to see which commit hash
:latest
corresponds to?