Re: LXD bootstrap inside KVM failed

If you set up a space in MAAS and you declare that the VM is in that space, then when you deploy something into a container, MAAS and Juju will coordinate to get a Container set up onto a bridge connected to the interface in the VM that is connected to the same space, with an IP address from the

Re: LXD bootstrap inside KVM failed

Thanks Alot mark for sharing your though i appreciate help from everyone in this forum. btw i am not the geek but i think i did it. for me below trick is working. Being part of the community i believe in sharing. i did it like this. on a system other then MAAS (Member of MAAS ofcourse) - ssh to

Re: LXD bootstrap inside KVM failed

Well, everything you want to do here is cleanly possible with MAAS, Juju and LXD, but you will need to dig into the tools and understand how the model in Juju describes machines and networking. Last, there is a particular set of gotchas around networking (which as you point out is the tricky

Re: LXD bootstrap inside KVM failed

Thank you very much for the understanding right Mark. yes you are connect i was doing that however on your advice i manage to install it on new VM now one step is clear. but the problem is i notice. LXD is creating its own subnet and hide the guest behind the NAT. now the problem is how can LAN

Re: LXD bootstrap inside KVM failed

On 08/08/17 08:31, Ante Karamatić wrote: > If you want to run LXD on the same host where bind is running, you > just have to configure bind to *not* listen on LXD network: > > https://www.cyberciti.biz/faq/unix-linux-bsd-bind-dns-listenon-configuration/ > > uto, 8. kol 2017. 09:04 Muhammad Yousuf

Re: LXD bootstrap inside KVM failed

If you want to run LXD on the same host where bind is running, you just have to configure bind to *not* listen on LXD network: https://www.cyberciti.biz/faq/unix-linux-bsd-bind-dns-listenon-configuration/ uto, 8. kol 2017. 09:04 Muhammad Yousuf Khan je napisao: > Thanks for

Re: LXD bootstrap inside KVM failed

Thanks for the update Ante. but since MAAS also used Bind for its own DNS resolution. how come one can use juju or lxd in absence of bind. any tip will be highly appreciated. Thanks, MYK On Tue, Aug 8, 2017 at 11:19 AM, Ante Karamatić < ante.karama...@canonical.com> wrote: > When one installs

Re: LXD bootstrap inside KVM failed

When one installs bind, and doesn't configure it, it listens on all interfaces. Since LXD uses dnsmasq on LXD network (which uses the same port as bind), starting dnsmasq fails and therefore LXD too. We should not disable people's bind, because they must have installed it for a reason. Maybe

Re: LXD bootstrap inside KVM failed

Having same issue. And wasted my whole day on this. now after loosing the battle. I am going to try this on physical server . Hope to see the solution for this. On Aug 8, 2017 6:52 AM, "Tim Penhey" wrote: > Yep, that is pretty strange. Why was bind running? > > Tim > >

Re: LXD bootstrap inside KVM failed

Yep, that is pretty strange. Why was bind running? Tim On 03/08/17 07:45, fengxia wrote: > For anyone, the solution is rather strange: > > $ sudo service stop bind9 > > $ sudo lxd start > > Reference: https://github.com/lxc/lxd/issues/2046 > > > On 08/02/2017 03:33 PM, fengxia wrote: >> Hi

Re: LXD bootstrap inside KVM failed

For anyone, the solution is rather strange: $ sudo service stop bind9 $ sudo lxd start Reference: https://github.com/lxc/lxd/issues/2046 On 08/02/2017 03:33 PM, fengxia wrote: Hi Juju, I have a 16.04 KVM. Installed juju and LXD from apt. $ juju bootstrap localhost test ERROR creating LXD

Re: LXD bootstrap inside KVM failed

Here is an update. Manually run this command, $ sudo lxd --group lxd Then $ lxc list works. So the LXD service was not started after reboot. Permission issue? On 08/02/2017 03:33 PM, fengxia wrote: Hi Juju, I have a 16.04 KVM. Installed juju and LXD from apt. $ juju bootstrap localhost