Re: [lxc-users] Will there be an extra section added to the LXD 2.0 blog post series for the new Networking capabilities?

On 2016-09-29 12:14, Stéphane Graber wrote: >It's not going to be part of the 2.0 series since it's not in LXD 2.0, >but I'll likely be posting something about the new network stuff in the >next few weeks. "cross-host tunnels with GRE or VXLAN" Interesting! Will it be limited to 2 LXD

Re: [lxc-users] Will there be an extra section added to the LXD 2.0 blog post series for the new Networking capabilities?

On Thu, Sep 29, 2016 at 12:11:06PM +0900, Tomasz Chmielewski wrote: > On 2016-09-29 12:03, Stéphane Graber wrote: > >On Wed, Sep 28, 2016 at 10:56:48PM -0400, brian mullan wrote: > >>The current 12 part blog post series is really helpful & informative: > >> >

Re: [lxc-users] Will there be an extra section added to the LXD 2.0 blog post series for the new Networking capabilities?

On 2016-09-29 12:03, Stéphane Graber wrote: On Wed, Sep 28, 2016 at 10:56:48PM -0400, brian mullan wrote: The current 12 part blog post series is really helpful & informative: https://www.stgraber.org/2016/03/11/lxd-2-0-blog-post-series-012/ But all the newly announced LXD 2.3 networking

Re: [lxc-users] Will there be an extra section added to the LXD 2.0 blog post series for the new Networking capabilities?

On Wed, Sep 28, 2016 at 10:56:48PM -0400, brian mullan wrote: > The current 12 part blog post series is really helpful & informative: > > https://www.stgraber.org/2016/03/11/lxd-2-0-blog-post-series-012/ > > But all the newly announced LXD 2.3 networking features >

[lxc-users] Mounting ISO files inside LXD container

I'm getting an error when I try to mount an ISO file into a container and I'm not sure how to fix the problem. I've searched a bit and found somewhat similar issues[1][2] but they were mostly related to LXC containers not LXD. When I try to mount an ISO I get an error: root@broodwar:~# mount -t

Re: [lxc-users] Q: Connecting a container to a static IP alias?

Greetings, Michael Peek! > On 09/27/2016 12:01 PM, Andrey Repin wrote: >> Just remove alias from host and configure the address inside a VM. > Thanks, that gets me one step closer. The VM has the right address on > the inside. But how do I get the *.117 address on the outside? There's no

Re: [lxc-users] Q: Connecting a container to a static IP alias?

On 09/27/2016 12:01 PM, Andrey Repin wrote: > Just remove alias from host and configure the address inside a VM. Thanks, that gets me one step closer. The VM has the right address on the inside. But how do I get the *.117 address on the outside? I tried creating the container with several

Re: [lxc-users] tun device in unprivileged Debian Stretch lxc Container

On 09/22/2016 05:14 PM, Paul Dino Jones wrote: Hi all, I could have sworn in the past I was able to make an unprivileged container use openvpn, but yesterday, i started an unprivileged container and was not able to use openvpn because I did not have a /dev/net/tun. I was able to get it started

Re: [lxc-users] tun device in unprivileged Debian Stretch lxc Container

On 09/28/2016 07:11 AM, Mike Wright wrote: On 09/22/2016 05:14 PM, Paul Dino Jones wrote: Hi all, I could have sworn in the past I was able to make an unprivileged container use openvpn, but yesterday, i started an unprivileged container and was not able to use openvpn because I did not have a

Re: [lxc-users] tun device in unprivileged Debian Stretch lxc Container

you need to map the device (lxc config), no need to do mknod in container. 2016-09-23 2:14 GMT+02:00 Paul Dino Jones : > Hi all, > > I could have sworn in the past I was able to make an unprivileged > container use openvpn, but yesterday, i started an unprivileged >