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

Removal of exposed ports #82

Open
smebberson opened this issue Mar 29, 2017 · 2 comments
Open

Removal of exposed ports #82

smebberson opened this issue Mar 29, 2017 · 2 comments

Comments

@smebberson
Copy link
Owner

Raised by @rbellamy, his suggestion is to remove exposed ports, and have this as a requirement of any users in their upstream images.

I agree with the theory. But how will we handle user expectation and UX in terms of actually using the images?

@rbellamy
Copy link
Contributor

rbellamy commented Apr 4, 2017

This comes down to answering the following question:

Is this repository for end-point images, or for folks that will use these images to derive end-point images?

That is a mission-statement level question that has to be answered.

@gdraheim
Copy link

As I using third party containers quite regulary, I found them to have some exposed ports that I do not need (and even more so a number of volumes). To help with the situation, I have created a little script to edit the metadata of a pulled image before internal use. Have a look at https://github.com/gdraheim/docker-copyedit for the workaround that docker/dockefiles can not unexpose ports.

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

No branches or pull requests

3 participants