-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Expose SCTP port support #6294
Comments
Hello Shin, I was thinking of running a container with docker sock mounted , and run docker sctp expose command at entrypoint. Is that good approach ? Thanks in advance, |
Beware of this cgroups limit issue: |
AIUI the support from docker/docker-py#2281 will enable this without further changes. So, closing. |
Hello Dear Support!
Is your feature request related to a problem? Please describe.
My problem is that compose only supports TCP and UDP port protocol types when exposing services ports, although it was already [implemented]
(moby/moby#9689 (comment)) in docker since 18.03.
And explained here
Trying to run the following:
The same with TCP is success:
I was wandering if you are planning to align compose acceptable values to respect expose port using SCTP protocol and convert to correct docker commands.
If I understand correctly, that concludes only extending the list of allowed values (tcp,udp,sctp)
Describe the solution you'd like
I would like docker-compose to respect sctp as it is an industry standard and widely used in telco's environments.
The example docker-compose.yml could look like:
Describe alternatives you've considered
I've considered running docker manually with -p flag.
For example ... -p 3868:3868/sctp
Additional context
As an additional context, I can provide few links related:
https://docs.docker.com/network/links/
http://laforge.gnumonks.org/blog/20170503-docker-overhyped/
Thanks,
Michael
The text was updated successfully, but these errors were encountered: