You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
The text was updated successfully, but these errors were encountered: