Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make PRIVATE_PORT optional for docker compose port #11859

Open
crazybolillo opened this issue May 29, 2024 · 1 comment
Open

Make PRIVATE_PORT optional for docker compose port #11859

crazybolillo opened this issue May 29, 2024 · 1 comment

Comments

@crazybolillo
Copy link

Description

"Normal" docker already does this. See the usage for docker port:

$ docker port --help

Usage: docker port CONTAINER [PRIVATE_PORT[/PROTO]]

However docker compose differs:

$ docker compose port --help

Usage:  docker compose port [OPTIONS] SERVICE PRIVATE_PORT

I can look into making a PR if you agree this should be optional.

@ndeloof
Copy link
Contributor

ndeloof commented May 29, 2024

makes sense we align with the docker port command
I can't wait for your PR :)

crazybolillo added a commit to crazybolillo/compose that referenced this issue Jun 1, 2024
This comand no longer needs a mandatory port. If no port is provided it
will instead list all published ports. This behavior falls in line with
the behavior provided by `docker port`.

Closes docker#11859.

Signed-off-by: Antonio Aguilar <[email protected]>
crazybolillo added a commit to crazybolillo/compose that referenced this issue Jun 1, 2024
This comand no longer needs a mandatory port. If no port is provided it
will instead list all published ports. This behavior falls in line with
the behavior provided by `docker port`.

Closes docker#11859.

Signed-off-by: Antonio Aguilar <[email protected]>
crazybolillo added a commit to crazybolillo/compose that referenced this issue Jun 1, 2024
This comand no longer needs a mandatory port. If no port is provided it
will instead list all published ports. This behavior falls in line with
the behavior provided by `docker port`.

Closes docker#11859.

Signed-off-by: Antonio Aguilar <[email protected]>
crazybolillo added a commit to crazybolillo/compose that referenced this issue Jun 1, 2024
This comand no longer needs a mandatory port. If no port is provided it
will instead list all published ports. This behavior falls in line with
the behavior provided by `docker port`.

Closes docker#11859.

Signed-off-by: Antonio Aguilar <[email protected]>
crazybolillo added a commit to crazybolillo/compose that referenced this issue Jun 4, 2024
This comand no longer needs a mandatory port. If no port is provided it
will instead list all published ports. This behavior falls in line with
the behavior provided by `docker port`.

Closes docker#11859.

Signed-off-by: Antonio Aguilar <[email protected]>
crazybolillo added a commit to crazybolillo/compose that referenced this issue Jun 4, 2024
This comand no longer needs a mandatory port. If no port is provided it
will instead list all published ports. This behavior falls in line with
the behavior provided by `docker port`.

Closes docker#11859.

Signed-off-by: Antonio Aguilar <[email protected]>
crazybolillo added a commit to crazybolillo/compose that referenced this issue Jun 12, 2024
This comand no longer needs a mandatory port. If no port is provided it
will instead list all published ports. This behavior falls in line with
the behavior provided by `docker port`.

Closes docker#11859.

Signed-off-by: Antonio Aguilar <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants