Have two containers listen on same udp port
I have two applications that listen to port 3000 for UDP packets. If I run them natively, all is well.
Now, I would like to put them in Docker containers. But it appears that the process of publishing to port 3000 in the docker compose file like so:
ports:
-"3000:3000/udp"
... creates an exclusive bind on the host's port 3000 such that the second container fails to publish its port.
Is there any way to allow two containers to do a non-exclusive bind to receive UDP traffic on the same port? I'm wondering if there is some way to tell docker to set SO_REUSEPORT to true when it does the bind.
Or maybe there is some other way to do what I need?
docker udp
asked Nov 13 at 21:00
Eric
6131820
add a comment |
I have two applications that listen to port 3000 for UDP packets. If I run them natively, all is well.
Now, I would like to put them in Docker containers. But it appears that the process of publishing to port 3000 in the docker compose file like so:
ports:
-"3000:3000/udp"
... creates an exclusive bind on the host's port 3000 such that the second container fails to publish its port.
Is there any way to allow two containers to do a non-exclusive bind to receive UDP traffic on the same port? I'm wondering if there is some way to tell docker to set SO_REUSEPORT to true when it does the bind.
Or maybe there is some other way to do what I need?
docker udp
asked Nov 13 at 21:00
Eric
6131820
is it really needed to have the port binding on the host port? normally if you have a multiple containers, each of them would expose the port 3000 and it would work fine since each container has its own ip
– Uku Loskit
Nov 13 at 23:07
add a comment |
I have two applications that listen to port 3000 for UDP packets. If I run them natively, all is well.
Now, I would like to put them in Docker containers. But it appears that the process of publishing to port 3000 in the docker compose file like so:
ports:
-"3000:3000/udp"
... creates an exclusive bind on the host's port 3000 such that the second container fails to publish its port.
Is there any way to allow two containers to do a non-exclusive bind to receive UDP traffic on the same port? I'm wondering if there is some way to tell docker to set SO_REUSEPORT to true when it does the bind.
Or maybe there is some other way to do what I need?
docker udp
asked Nov 13 at 21:00
Eric
6131820
I have two applications that listen to port 3000 for UDP packets. If I run them natively, all is well.
Now, I would like to put them in Docker containers. But it appears that the process of publishing to port 3000 in the docker compose file like so:
ports:
-"3000:3000/udp"
... creates an exclusive bind on the host's port 3000 such that the second container fails to publish its port.
Is there any way to allow two containers to do a non-exclusive bind to receive UDP traffic on the same port? I'm wondering if there is some way to tell docker to set SO_REUSEPORT to true when it does the bind.
Or maybe there is some other way to do what I need?
docker udp
docker udp
asked Nov 13 at 21:00
Eric
6131820
asked Nov 13 at 21:00
Eric
6131820
asked Nov 13 at 21:00
Eric
6131820
asked Nov 13 at 21:00
Eric
6131820
asked Nov 13 at 21:00
Eric
6131820
6131820
is it really needed to have the port binding on the host port? normally if you have a multiple containers, each of them would expose the port 3000 and it would work fine since each container has its own ip
– Uku Loskit
Nov 13 at 23:07
add a comment |
is it really needed to have the port binding on the host port? normally if you have a multiple containers, each of them would expose the port 3000 and it would work fine since each container has its own ip
– Uku Loskit
Nov 13 at 23:07
is it really needed to have the port binding on the host port? normally if you have a multiple containers, each of them would expose the port 3000 and it would work fine since each container has its own ip
– Uku Loskit
Nov 13 at 23:07
is it really needed to have the port binding on the host port? normally if you have a multiple containers, each of them would expose the port 3000 and it would work fine since each container has its own ip
– Uku Loskit
Nov 13 at 23:07
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53289424%2fhave-two-containers-listen-on-same-udp-port%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53289424%2fhave-two-containers-listen-on-same-udp-port%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
is it really needed to have the port binding on the host port? normally if you have a multiple containers, each of them would expose the port 3000 and it would work fine since each container has its own ip
– Uku Loskit
Nov 13 at 23:07