latest version docker startup issue?

[traceypooh]

docker run -p 80:80 ghcr.io/esm-dev/esm.sh:latest
docker run -p 80:80 ghcr.io/esm-dev/esm.sh:v137

doesnt seem to work, kind of does nothing.
I've tried running container interactively and tried making a baseline config.json file, tried switching port to 8080 and more.

any clues?

v135 works, v136 i might be having a little bit of issues with with our CI/CD automation to self-host the deploy. but we'd like to get to v137...

TIA!

[nicky9door]

It seems like the esmd bin doesn't exist in the ghcr image.

When trying to build from the Dockerfile, the build fails on the step that copies the glibc libraries for deno. Not sure if that's causing the issues with the GHCR image.

It looks like alpine now has a deno pkg so perhaps that could be used instead of having to copy the glibc libraries?

[nicky9door]

I took another look at this issue. There are a few things to consider:

• The startup issue is due to the fact that the default port was changed from 8080 to 80. The container runs as a non root user which by default cannot bind to ports < 1024
• The newer versions of esmd write directly to a log file instead of outputting to stdout so there is no feedback to the user that an error occurs. You have to use docker exec to run a bash shell and then look at the log to see the permission failed
• It seems like newer versions don't allow the port to be configured via environment variable. You need to explicitly pass a json config file with a non privileged port configured in order to get the container to start. There's no feedback to indicate it's working correctly due to the logging change, other than the fact that the container doesn't immediately stop

[ije]

it just works for me.