[lxc-users] sub-domains for different lxc bridge networks

[Veselin Sinanov]

This sound interesting, I can try it.

 

What actually I am trying to achieve, is to be able to create many sub-networks, each one of them contains many LXC containers. The containers within given sub-network will communicate only in that network, and each sub-network will need to have access point (an one single container) accessible from outside (now it is not restricted only to HTTP, but all possible protocols and ports).

 

What I am trying to achieve is some sort cloud infrastructure in my home. Maybe I need to check the Open Stack … may you advice.

 

Best

 

From: lxc-users [mailto:lxc-users-bounces at lists.linuxcontainers.org] On Behalf Of Benoit GEORGELIN - Association Web4all
Sent: Friday, November 11, 2016 6:45 PM
To: lxc-users
Subject: Re: [lxc-users] sub-domains for different lxc bridge networks

 

Hello,

 

I have single static IP address from my ISP. I have registered DNS name (root-domain.com for example) mapped to that public IP. 

 

I have an router (Linksys E1700) and home network. 

 

I want to create specific sub-domain (sub1.root-domain.com – for example), register it on DNS provider, and point it to specific LXC container. 

And then I want to create second sub-domain (sub2.root-domain.com), register it on DNS provider, and mapped it to second LXC container.

 

Both containers are running inside host machine which is behind the router (Linksys E1700).

 

The router is accessible from public, because it got assigned public IP address from ISP, but how I should configure the rest of the LXC containers?

 

Please, advice.

 

-Veselin


_______________________________________________
lxc-users mailing list
lxc-users at lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

 

Hi , if your concern is only about HTTP(s) (and eventually some TCP) what you want to do is basically an infrastructure with 3 containers :

 

1- Reverse proxy HTTP like Haproxy)

2- Container for domain1

2- Container for domain2 

 

DNS for domain1 and domain2 goes to your public IP address 
HTTP(s) port goes to you Reverse Proxy Container (port forwarding) on your local network 

Rules match the domaine name on the reverse proxy to server the content on the right container 

 

LXC container should only be able to communicate with your local network 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20161111/49b4da80/attachment.html>