Re: [lxc-users] Bind public IP that is available on host's ens3:1 to a specific LXD container?

Hi Thomas, Can you list the steps you went through to get it working? I'm in the same boat. thanks. On Fri, May 19, 2017 at 8:31 PM, Thomas Ward wrote: > Thanks to some off-list replies and some help from other online > resources, I've been able to switch this to a bridged

Re: [lxc-users] Bind public IP that is available on host's ens3:1 to a specific LXD container?

Great suggestions from Fajar. A couple more ideas if you only have one public IP on your container: * Use HAProxy on the container’s main IP address with Server Name Identification (SNI) and a local DNS server. This way, all your sites are tied to the same IP address as the container with

Re: [lxc-users] Bind public IP that is available on host's ens3:1 to a specific LXD container?

On Sat, May 20, 2017 at 10:31 AM, Thomas Ward wrote: > I've been able to switch this to a bridged method, with the > host interfaces set to 'manual', an inet0 bridge created that is static > IP'd for the host system to have its primary IP, and can have manual IP > assignments

Re: [lxc-users] Bind public IP that is available on host's ens3:1 to a specific LXD container?

Hello Thomas, I use a nginx-reverse-proxy for accessing the container(s) webspace(s). If I need to access something (a specific port) of a container from the outside world, I use iptables to reach it, in your case i.e. to access your containers ssh-server (on outside-port 22022) you can use:

Re: [lxc-users] Bind public IP that is available on host's ens3:1 to a specific LXD container?

Thanks to some off-list replies and some help from other online resources, I've been able to switch this to a bridged method, with the host interfaces set to 'manual', an inet0 bridge created that is static IP'd for the host system to have its primary IP, and can have manual IP assignments to

[lxc-users] Bind public IP that is available on host's ens3:1 to a specific LXD container?

Hello. I've got a VDS from RamNode - which is essentially a KVM VPS with dedicated CPUs, and larger RAM capacity. This VDS has three IPs. I'm going to obfuscate them here, but essentially the host box is configured like this: # The primary network interface auto ens3 iface ens3 inet static