Skip to content

Container starts on non available port #87

Open
@Carael

Description

@Carael

Squadron containers uses automatic port assignment from Docker. The ports range starts from 32768 to 61000 and increments with every container created. If the port is already taken the docker api doesn't throw an exception or takes next port. It's also unclear how to reset the current port counter that's assigned since it's persisted across pc restarts or even docker removal from pc.

A bug is created on Docker Cli.

Possible solution is to set other port range on the system itself like described here .

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