Why does `--publish` option for a port range shows individual entries in podman ?
Issue
- If the port range is huge, the container takes little more time to come up.
- Because of individual entries for each port in the port range, podman inspect produces a huge output
Environment
- RHEL 8
- Podman
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.