You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have built a stack for uploading COGs and serve them from a storage bucket server. If I add marblecutter-virtual to the stack in a docker-compose deployment all its endpoints don't work as expected if the querystring url is from the same domain/ip while they work if it is an external cog like that from the readme.
The URL you're then using as url is http://192.168.99.100:30800/api/cogs/geotiff-with-ovr.tif?
My initial guess is that the Docker image isn't able to connect to that IP from within. To verify, run docker-compose exec marblecutter-virtual bash (while the stack is running) and from within that, curl -v <url> > /dev/null to see if it can connect. If not, you may be able to use http://webapi/api/cogs/geotiff-with-ovr.tif as the URL (webapi will resolve to the corresponding container's IP). (You may need to add a links section with webapi for the marblecutter-virtual service for them to be linked up network- and DNS-wise.)
Thanks @mojodna, I will definitively try it out. Anyway I have also tried with cloud kubernetes clusters and having the marblecutter container in a different k8s cluster from the webapi one everything works very well. Still not checked it into the same minikube.
Need more investigations
I have built a stack for uploading COGs and serve them from a storage bucket server. If I add marblecutter-virtual to the stack in a docker-compose deployment all its endpoints don't work as expected if the querystring
url
is from the same domain/ip while they work if it is an external cog like that from the readme.There is a docker-compose to reproduce the problem.
Just upload a geotiff with tiled overviews as the example below:
The text was updated successfully, but these errors were encountered: