LukeChannings/moviematch

[Bug] Port set in docker-compose apparently not used by moviewatch

Closed this issue · 2 comments

ohtee commented

Describe the bug
Port set in docker-compose not used by moviewatch

To Reproduce
In docker-compose.yml, use:
ports:
- 7999:7999

then docker-compose up -d

In the browser at my NAS's IP address:7999 I cycle between ERR_EMPTY_RESPONSE and ERR_CONNECTION_RESET

So I checked the container's log which states: "INFO Listening on port 8000"

Expected behavior

Load at the port set in the compose file.

Additional context

This is on a Synology NAS.

LukeChannings commented

Hey @ohtee

If you need to change the port that MovieMatch listens on you can set the PORT environment variable (e.g. PORT=7999).

Is there a reason you don't want to set the following in your docker-compose?

ports:
  - 7999:8000

Please see the compose file documentation for ports and environment, as well as MovieMatch's available configuration options for available environment variables.

ohtee commented

That solved it, thanks! I'm an idiot and it's not the first time I get confused between host ports and container ports.