[Bug]: Container fails to start using latest GeoLibre docker image

[sindile]

Before you start

• I searched the existing issues and did not find a duplicate.
• This is a bug report, not a usage question (questions belong in Discussions).

What happened?

I have pulled the latest GeoLibre image Digest: sha256:b6bf7e69c0c0bbc8bfd5cbdcb3f7af0482c974c18e3bd98e62268a4c4b3d4d62

running docker run --rm -p 127.0.0.1:9087:80 ghcr.io/opengeos/geolibre:latest results in this error message:
File "", line 75
f"(or {loopback_schemes[0]}:// on {/.join(loopback_hosts)}), not {value!r}."
^
SyntaxError: f-string: expecting a valid expression after '{'

Steps to reproduce

1. docker pull ghcr.io/opengeos/geolibre:latest
2. docker run --rm -p 127.0.0.1:9087:80 ghcr.io/opengeos/geolibre:latest

Expected behavior

I expected the GeoLibre container to start

How are you running GeoLibre?

Web - http://127.0.0.1:9087/

Operating system and browser

No response

Sample data

No response

Screenshots or logs

No response

[giswqs]

Reproduced on your exact digest, and confirmed the cause.

docker/entrypoint.sh builds its runtime-config program as a single-quoted python -c '...' argument. Line 205 of that script reads:

f"(or {loopback_schemes[0]}:// on {'/'.join(loopback_hosts)}), not {value!r}."

The apostrophes around / close the shell's quoting, so Python receives {/.join(loopback_hosts)} instead. Since python -c compiles the whole program before running any of it, this is a boot failure for every container regardless of configuration, and set -e turns it into an immediate exit. That is why you see it on a plain docker run with no environment variables set.

It arrived with #1687 (runtime share/collab configuration), which is why older images are unaffected.

Fixed in #1690, which joins the / outside the f-string using double quotes. Verified against the image built from that branch using your command:

$ docker run --rm -p 127.0.0.1:9087:80 <branch build>
INFO:     Application startup complete.
$ curl -o /dev/null -w '%{http_code}' http://127.0.0.1:9087/
200

Thanks for the clear report; the digest made this quick to pin down.