Skip to content

Allow services with published ports to be scaled to 1 #1133

@jamshid

Description

@jamshid

How about allowing services with a published port (eg, "80:80") to be "scaled" to "1" or "0". Report the below error only when scaling >=2. Sorry I know this is a nit, but seems slightly better behavior and would simplify some scripts.

$ docker-compose scale myserver=1
Service "myserver" cannot be scaled because it specifies a port on the host. If multiple containers for this service were created, the port would clash.

Remove the ":" from the port definition in docker-compose.yml so Docker can choose a random port for each container.

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