There was an issue loading URL from $image value when using Path to the mounted folder OR http path to served images in different container.

[NathanHGayle]

Hi Team,

I'm attempting to upload pre-annotated images via a JSON file. Ideally, I want to avoid using the local storage setup approach and would prefer to serve the local images via the same docker container, or a different docker container on the same network, then use the URL within the task e.g.:
"image":"http://{container_id)/label-studio/data/folder_one/folder_two/folder_three/folder_four/image.png⁠"
OR
"image": "http://localhost:XXXX/image.png".

It's not working as described so any suggestions?

Kind regards
Nathan

[heidi-humansignal]

Hi Nathan,
You can absolutely use HTTP URLs in tasks, but there are a few gotchas when the images are served from Docker containers. The browser (not the Label Studio server) fetches the image, so the URL must be reachable from your browser and satisfy CORS and scheme (http/https) rules.
Here are two workable approaches. The first lets you keep using an external HTTP server; the second is the built‑in local-files server that avoids CORS entirely.

1. Keep using an HTTP server (no Local Storage UI required)

• Expose a static file server to your host so the browser can reach it. Don’t use container_id in the URL; the browser won’t resolve Docker-internal hostnames.
• Ensure CORS allows the Label Studio origin.
• Ensure the URL scheme matches (if LS is https, the image must be https to avoid mixed content).

Thank you,
Abu

Comment by Abubakar Saad
Workflow Run

[NathanHGayle]

Thanks for this, I ended up using the local storage route but thoroughly appreciate the quick response!

[heidi-humansignal]

No problem. Sounds good, I'll mark this ticket as solved.

Thank you,
Abu

Comment by Abubakar Saad
Workflow Run