{"action":"opened","issue":{"url":"https://api.github.com/repos/sclorg/s2i-nodejs-container/issues/199","repository_url":"https://api.github.com/repos/sclorg/s2i-nodejs-container","labels_url":"https://api.github.com/repos/sclorg/s2i-nodejs-container/issues/199/labels{/name}","comments_url":"https://api.github.com/repos/sclorg/s2i-nodejs-container/issues/199/comments","events_url":"https://api.github.com/repos/sclorg/s2i-nodejs-container/issues/199/events","html_url":"https://github.com/sclorg/s2i-nodejs-container/issues/199","id":391225484,"node_id":"MDU6SXNzdWUzOTEyMjU0ODQ=","number":199,"title":"Don't expose port 8080 by default","user":{"login":"mcandre","id":5316,"node_id":"MDQ6VXNlcjUzMTY=","avatar_url":"https://avatars1.githubusercontent.com/u/5316?v=4","gravatar_id":"","url":"https://api.github.com/users/mcandre","html_url":"https://github.com/mcandre","followers_url":"https://api.github.com/users/mcandre/followers","following_url":"https://api.github.com/users/mcandre/following{/other_user}","gists_url":"https://api.github.com/users/mcandre/gists{/gist_id}","starred_url":"https://api.github.com/users/mcandre/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mcandre/subscriptions","organizations_url":"https://api.github.com/users/mcandre/orgs","repos_url":"https://api.github.com/users/mcandre/repos","events_url":"https://api.github.com/users/mcandre/events{/privacy}","received_events_url":"https://api.github.com/users/mcandre/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-14T18:51:45Z","updated_at":"2018-12-14T18:51:45Z","closed_at":null,"author_association":"NONE","body":"Many Node.js applications use a different port, or even avoid using networking altogether (such as Node.js CLI tools). I think the benefits of assigning a default port mapping are slim compared to the downsides of collision for different kinds of Node.js project configurations.\r\n\r\nOne workaround for downstream images is to reconfigure applications to match port 8080. Another workaround is to open up both 8080 and the other ports (unfortunately, Docker does not currently have a way to un-`EXPOSE` ports). Ultimately, it would be cleaner to not assume any particular network port configuration and leave that up to downstream developers to decide."}}
{"actor":{"display_login":"mcandre"}}