You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It turns out that although podman-compose does not support it, docker-compose can forward dynamic port ranges to a port on multiple containers of the same service.
So ports 24716 through 24816 (on the host) can be forwarded to 101 pulp_content containers, all listening on port 24816.
Similarly, 24817 through 24917 (on the host) can be forwarded to 101 pulp_content containers, all listening on port 24817.
podman-compose will ignore this syntax without erroring.
The text was updated successfully, but these errors were encountered:
It turns out that although podman-compose does not support it, docker-compose can forward dynamic port ranges to a port on multiple containers of the same service.
So ports 24716 through 24816 (on the host) can be forwarded to 101 pulp_content containers, all listening on port 24816.
Similarly, 24817 through 24917 (on the host) can be forwarded to 101 pulp_content containers, all listening on port 24817.
podman-compose will ignore this syntax without erroring.
The text was updated successfully, but these errors were encountered: