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

Force compose to use conventional ports #243

Merged
merged 1 commit into from
Jan 13, 2021

Conversation

kahowell
Copy link
Contributor

I only noticed b/c podman-compose down followed by podman-compose up broke my dev setup.

So, the difference between 5432 and 5432:5432:

  • 5432 instructs podman to pick an arbitrary port to map to a container's port 5432
  • 5432:5432 instructs podman to map the host's port 5432 to a container's port 5432

podman v2.2.0+ ensures that the arbitrary port is random.

See containers/podman#7947

I only noticed b/c `podman-compose down` followed by `podman-compose up`
broke my dev setup.

So, the difference between `5432` and `5432:5432`:

 - `5432` instructs podman to pick an arbitrary port to map to a
   container's port `5432`
 - `5432:5432` instructs podman to map the host's port `5432` to a
   container's port `5432`

podman v2.2.0+ ensures that the arbitrary port is random.

See containers/podman#7947
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@lindseyburnett lindseyburnett merged commit 0ba0de4 into develop Jan 13, 2021
@lindseyburnett lindseyburnett deleted the khowell/container-compose-ports branch January 13, 2021 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants