Feature Request: Support Creating Containers Without Host Port Bindings #2337
RuBeeN-cmd
started this conversation in
Ideas
Replies: 2 comments 4 replies
-
|
without port is possible already, but that is for no port at all. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
im not sure im understanding completely. you can already make the containers local only by binding them to 127.0.0.1, then you only bind the container that needs external access to the actual ip of the machine. its not the exact same, but thats how i run my minecraft servers and a proxy managing them. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
It would be useful to support creating webserver containers without binding ports on the host machine. This would allow services to remain accessible only within the pelican_nw network, making it easier to place a reverse proxy in front of them for controlled external access.
Beta Was this translation helpful? Give feedback.
All reactions