Skip to content
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

Add ability to expose ports instead of publish them. #744

Open
Renari opened this issue Oct 30, 2024 · 2 comments
Open

Add ability to expose ports instead of publish them. #744

Renari opened this issue Oct 30, 2024 · 2 comments

Comments

@Renari
Copy link

Renari commented Oct 30, 2024

This would allow you to use a reverse proxy to publish instead of exposing ports on the host for every application.

@stavros-k
Copy link
Contributor

I think an option to just not publish them to host (per port) should be enough.
expose is not really doing something, its mostly informative.

https://docs.docker.com/reference/dockerfile/#expose

That being said, this option would only make sense if there is also custom network support.
(Correct my if I'm wrong) But 2 services in different stacks cannot communicate internally unless they are joined on the same custom network.

@Renari
Copy link
Author

Renari commented Nov 1, 2024

(Correct my if I'm wrong) But 2 services in different stacks cannot communicate internally unless they are joined on the same custom network.

I do believe that to be true, which is why #743 was also opened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants