💡 Feature request: Custom port
Closed this issue · 3 comments
Is your feature request related to a problem? Please describe.
Please add an option to specify the internal port redlib listens to.
Describe the feature you would like to be implemented
Add a environment variable like REDLIB_PORT to be able to specify a value other than 8080.
Describe alternatives you've considered
You are currently able to define a different port on the outside (just like with every other docker container) like: --port 1234:8080. However, if you're for example using network_mode: host you're out of luck here :/
You can already do something like redlib -p 8081 to swap to port 8081. Not too familiar with docker so I'm not sure if you can easily change the command it runs, but it's a workaround if you can.
So looks like this is already possible by using the env PORT, but it's not been documented yet. I opened a PR for it.
What scenarios would you use network instead of bridge? Asking out of curiosity, I'm still a docker noob.
Also, it appears redlib is the only container that I run that appears to be in host mode. Using the following command,
docker inspect --format='{{.NetworkSettings.Networks}}' <container>
all other docker containers show map[bridge:<...>] or something similar. But redlib shows map[<myhostname>_default:<...>]. Any advice would be appreciated.