Skip to content

Invalid Port Exposed error #188

@dejwsz

Description

@dejwsz

I had such error " Invalid Port Exposed (Possible Bug)" with that part in my Dockerfile:

ARG PORT=5000
ENV PORT $PORT
EXPOSE $PORT

Is that a wrong approach? The idea behind is to have an option to steer the exposed port value during a build time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions