How to make a Docker VPN gateway for other Docker containers & stacks?












0














We are implementing a CI infrastructure as Docker stacks.



Some of the containers in the stacks now need to access external services, only available through an OpenVPN connection, let's say on the 192.168.2.0/24 subnet.



In order to keep containers as "single-purpose" as possible, we would ideally like to add a Docker container acting as a VPN gateway, through which other containers could talk to the 192.168.2.0/24 subnet.



This first raises a complication: a VPN client containers needs the cap-add of NET_ADMIN, which is not available in the swarm mode we are using to deploy stack. Is there a work around, appart from starting the VPN client container as standalone through docker run?



And more importantly, once we have the vpnclient container running and connected, how can we configure other containers in the swarm to actually use it as a gateway to reach all IPs on the 192.168.2.0/24 subnet?










share|improve this question






















  • This might be helpful github.com/dperson/openvpn-client
    – Jacob Tomlinson
    Nov 22 at 11:10










  • @JacobTomlinson Thank you for the pointer! Sadly, it seems that their proposal for client containers to go through the gateway container is to start them with --net=container:vpn, which is not available for Docker stacks afaik.
    – Ad N
    Nov 22 at 11:46












  • Ah thats a shame. That is the way I'm using it at the moment.
    – Jacob Tomlinson
    Nov 22 at 14:51
















0














We are implementing a CI infrastructure as Docker stacks.



Some of the containers in the stacks now need to access external services, only available through an OpenVPN connection, let's say on the 192.168.2.0/24 subnet.



In order to keep containers as "single-purpose" as possible, we would ideally like to add a Docker container acting as a VPN gateway, through which other containers could talk to the 192.168.2.0/24 subnet.



This first raises a complication: a VPN client containers needs the cap-add of NET_ADMIN, which is not available in the swarm mode we are using to deploy stack. Is there a work around, appart from starting the VPN client container as standalone through docker run?



And more importantly, once we have the vpnclient container running and connected, how can we configure other containers in the swarm to actually use it as a gateway to reach all IPs on the 192.168.2.0/24 subnet?










share|improve this question






















  • This might be helpful github.com/dperson/openvpn-client
    – Jacob Tomlinson
    Nov 22 at 11:10










  • @JacobTomlinson Thank you for the pointer! Sadly, it seems that their proposal for client containers to go through the gateway container is to start them with --net=container:vpn, which is not available for Docker stacks afaik.
    – Ad N
    Nov 22 at 11:46












  • Ah thats a shame. That is the way I'm using it at the moment.
    – Jacob Tomlinson
    Nov 22 at 14:51














0












0








0







We are implementing a CI infrastructure as Docker stacks.



Some of the containers in the stacks now need to access external services, only available through an OpenVPN connection, let's say on the 192.168.2.0/24 subnet.



In order to keep containers as "single-purpose" as possible, we would ideally like to add a Docker container acting as a VPN gateway, through which other containers could talk to the 192.168.2.0/24 subnet.



This first raises a complication: a VPN client containers needs the cap-add of NET_ADMIN, which is not available in the swarm mode we are using to deploy stack. Is there a work around, appart from starting the VPN client container as standalone through docker run?



And more importantly, once we have the vpnclient container running and connected, how can we configure other containers in the swarm to actually use it as a gateway to reach all IPs on the 192.168.2.0/24 subnet?










share|improve this question













We are implementing a CI infrastructure as Docker stacks.



Some of the containers in the stacks now need to access external services, only available through an OpenVPN connection, let's say on the 192.168.2.0/24 subnet.



In order to keep containers as "single-purpose" as possible, we would ideally like to add a Docker container acting as a VPN gateway, through which other containers could talk to the 192.168.2.0/24 subnet.



This first raises a complication: a VPN client containers needs the cap-add of NET_ADMIN, which is not available in the swarm mode we are using to deploy stack. Is there a work around, appart from starting the VPN client container as standalone through docker run?



And more importantly, once we have the vpnclient container running and connected, how can we configure other containers in the swarm to actually use it as a gateway to reach all IPs on the 192.168.2.0/24 subnet?







docker openvpn docker-stack






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 at 10:23









Ad N

3,6512146




3,6512146












  • This might be helpful github.com/dperson/openvpn-client
    – Jacob Tomlinson
    Nov 22 at 11:10










  • @JacobTomlinson Thank you for the pointer! Sadly, it seems that their proposal for client containers to go through the gateway container is to start them with --net=container:vpn, which is not available for Docker stacks afaik.
    – Ad N
    Nov 22 at 11:46












  • Ah thats a shame. That is the way I'm using it at the moment.
    – Jacob Tomlinson
    Nov 22 at 14:51


















  • This might be helpful github.com/dperson/openvpn-client
    – Jacob Tomlinson
    Nov 22 at 11:10










  • @JacobTomlinson Thank you for the pointer! Sadly, it seems that their proposal for client containers to go through the gateway container is to start them with --net=container:vpn, which is not available for Docker stacks afaik.
    – Ad N
    Nov 22 at 11:46












  • Ah thats a shame. That is the way I'm using it at the moment.
    – Jacob Tomlinson
    Nov 22 at 14:51
















This might be helpful github.com/dperson/openvpn-client
– Jacob Tomlinson
Nov 22 at 11:10




This might be helpful github.com/dperson/openvpn-client
– Jacob Tomlinson
Nov 22 at 11:10












@JacobTomlinson Thank you for the pointer! Sadly, it seems that their proposal for client containers to go through the gateway container is to start them with --net=container:vpn, which is not available for Docker stacks afaik.
– Ad N
Nov 22 at 11:46






@JacobTomlinson Thank you for the pointer! Sadly, it seems that their proposal for client containers to go through the gateway container is to start them with --net=container:vpn, which is not available for Docker stacks afaik.
– Ad N
Nov 22 at 11:46














Ah thats a shame. That is the way I'm using it at the moment.
– Jacob Tomlinson
Nov 22 at 14:51




Ah thats a shame. That is the way I'm using it at the moment.
– Jacob Tomlinson
Nov 22 at 14:51

















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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428772%2fhow-to-make-a-docker-vpn-gateway-for-other-docker-containers-stacks%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428772%2fhow-to-make-a-docker-vpn-gateway-for-other-docker-containers-stacks%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Berounka

Sphinx de Gizeh

Different font size/position of beamer's navigation symbols template's content depending on regular/plain...