-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker Allow IP address binding #787
Comments
This would be an extremely helpful addition for those of us that want to bind a service to another interface, say for isolating services on a VLAN. Until this is available, I'm using custom docker-compose files for most of my services—which works fine for me and I'm happy enough with the option—but it would be nice to be able to use the apps catalogue. |
Hello, yes this is something that I want to add as well. |
That's fantastic; glad to hear it. Thanks! |
Not sure if another request is needed for this or if it falls here but binding to another containers network stack would be useful as well; such as in the case of sabnzbd or transmission binding to another containers running VPN. If needed I can open an additional request. |
According to the official docs we should be able to bind a container to a specific IP address.
This is super useful for applications that should only be exposed to a particular network and for reverse proxying from one network to another.
The text was updated successfully, but these errors were encountered: