On Sat, Mar 19, 2016 at 06:21:51AM +0700, Fajar A. Nugraha wrote:
> On Fri, Mar 18, 2016 at 11:09 PM, Sean McNamara wrote:
> > As part of that, I was expecting some way to tell LXD to restrict the
> > IP addresses that can be claimed/used by a given container. For
> > instance,
On Mar 21, 2016, at 2:26 AM, Andrey Repin wrote:
Greetings, Mahesh Patade!
> Hi,
> here is simple and sweet how to on bridge networking.
>
> https://insights.ubuntu.com/2015/11/10/converting-eth0-to-br0-and-getting-all-your-lxc-or-lxd-onto-your-lan/
> Google is your
Greetings, Mahesh Patade!
> Hi,
> here is simple and sweet howto on bridge networking.
>
> https://insights.ubuntu.com/2015/11/10/converting-eth0-to-br0-and-getting-all-your-lxc-or-lxd-onto-your-lan/
> Google is your friend. ;)
That's no better than LXCBR…
Try macvlan bridge one day.
--
Hi,
here is simple and sweet howto on bridge networking.
https://insights.ubuntu.com/2015/11/10/converting-eth0-to-br0-and-getting-all-your-lxc-or-lxd-onto-your-lan/
Google is your friend. ;)
On 21 Mar 2016 3:31 am, "Hans Deragon" wrote:
> Greetings,
>
> I solved my issue.
Greetings,
I solved my issue. Sean Mcnamara opened my eyes he wrote "First of all,
there's no such thing as LX[C|D]. You're either using LXC or LXD.".
This brought a paradigm shift where I though I use 'lxc' as the command,
now I search the web for "LXD 2.0 ". I then found
instructions for the
Greetings,
> The recommended way to manage IPs with LXD is to do it
> exactly the same way you would do it for your VMs or
> physical machines, so either configure your DHCP server to
> give a static lease or configure the container to use a
> static IP (you can use lxc file pull/push/edit to do
On Fri, Mar 18, 2016 at 12:09 PM, Sean McNamara wrote:
> On Fri, Mar 18, 2016 at 11:43 AM, Stéphane Graber wrote:
>> Our stance hasn't changed. LXD doesn't know nor care about layer-3
>> networking, all it does is setup your layer-2.
>>
>> Having LXD
Our stance hasn't changed. LXD doesn't know nor care about layer-3
networking, all it does is setup your layer-2.
Having LXD pre-initialize your network namespace confuses the heck out
of a bunch of distros which expect all network to be unconfigured by the
time they apply their own config (they
First of all, there's no such thing as LX[C|D]. You're either using
LXC or LXD. They're different enough in their configuration and
operation that you can't ask an "either-or" question. Pick one
solution and focus on that.
I just wanted to chime in to say that I have this same question. I'm
stuck
Greetings,
Ok, this is ridiculous and I apologize for asking help for such a simple
task, but I fail to find the answers by myself. I fail to find proper
documentation to setup bridge networking and static IP. Newbie here btw
and setup details at the end of this email.
I got the container
On Fri, Mar 18, 2016 at 11:43 AM, Stéphane Graber wrote:
> Our stance hasn't changed. LXD doesn't know nor care about layer-3
> networking, all it does is setup your layer-2.
>
> Having LXD pre-initialize your network namespace confuses the heck out
> of a bunch of distros
On Fri, Mar 18, 2016 at 12:15:35PM -0400, Sean McNamara wrote:
> On Fri, Mar 18, 2016 at 12:09 PM, Sean McNamara wrote:
> > On Fri, Mar 18, 2016 at 11:43 AM, Stéphane Graber
> > wrote:
> >> Our stance hasn't changed. LXD doesn't know nor care about layer-3
On Fri, Mar 18, 2016 at 11:09 PM, Sean McNamara wrote:
> As part of that, I was expecting some way to tell LXD to restrict the
> IP addresses that can be claimed/used by a given container. For
> instance, if I have a public Internet IPv4 /26 allocated to a physical
> host by a
13 matches
Mail list logo