Skip to content

Don't expose port 8080 by default #199

@mcandre

Description

@mcandre

Many Node.js applications use a different port (e.g., React.js assumes 3000), or even avoid using networking altogether (e.g., 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.

One 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions