Well In fact, my solution made my DNS resolution quite fucked up. Every
'apt update' freezes at 0% for 30 sec.
Even with Gregory's solution, adding auth-zone and dns-loop-detect in
lxc network config, I've got the same issue.
However, it does not seem to eat my cpu.
Le 18/04/2017 à 02:12, Grego
Hi Gregory,
thanks! The 100% cpu usage is gone!
I'm using lxC, so I had to "hack" your instructions.
/etc/default/lxc-net:
LXC_DHCP_CONFILE=/etc/lxc/dnsmasq.conf
/etc/lxc/dnsmasq.conf:
dns-loop-detect
auth-zone=lxc
But now I cannot resolve external domains from inside the containers,
and I kn
Norbento, indeed you are not crazy! I have seen the same thing here.
On my laptop I did the nm-applet setup to setup dns on lxdbr0, and then saw
cpu usage spike to 100% due to a loop about dnsmasq asking the
network-manager dns server and back around forever...
the way I fixed this was by adding t
That used to work, but from 17.04 (on the desktop editions, both
ubuntu and kubuntu) adding the ip of the bridge to /etc/resolv.conf
makes systemd-resolved and dnsmasq eat my cpu.
2017-04-17 12:16 GMT-03:00 Matlink :
> For me, simply adding the lxc bridge IP address to DNS resolvers made me
> able
Yes, added it via network manager GUI (nm-applet)
--
Matlink
Le 17 avril 2017 18:44:57 GMT+02:00, Simos Xenitellis
a écrit :
>On Mon, Apr 17, 2017 at 6:16 PM, Matlink wrote:
>> For me, simply adding the lxc bridge IP address to DNS resolvers made
>me
>> able to resolve *.lxd domains from the h
On Mon, Apr 17, 2017 at 6:08 PM, Norberto Bensa
wrote:
> Hello Simos,
>
>
> I did all my experiments on clean ubuntu (desktop) and kubuntu
> installs because I don't trust the kubuntu installed in my notebook
> :-)
>
> Your instructions work until 16.10. Can you verify your instructions
> work on
On Mon, Apr 17, 2017 at 6:16 PM, Matlink wrote:
> For me, simply adding the lxc bridge IP address to DNS resolvers made me
> able to resolve *.lxd domains from the host machine.
Which configuration files are you referring to in this case?
Are you referring to the GUI configuration of a network in
For me, simply adding the lxc bridge IP address to DNS resolvers made me able
to resolve *.lxd domains from the host machine.
--
Matlink
Le 17 avril 2017 13:42:36 GMT+02:00, Simos Xenitellis
a écrit :
>On Thu, Apr 13, 2017 at 10:49 PM, Norberto Bensa
> wrote:
>> Hello Simos,
>>
>> 2017-04-13 1
Hello Simos,
I did all my experiments on clean ubuntu (desktop) and kubuntu
installs because I don't trust the kubuntu installed in my notebook
:-)
Your instructions work until 16.10. Can you verify your instructions
work on a fresh (k)ubuntu desktop 17.04?
Thanks!
Regards,
Norberto
2017-
On Thu, Apr 13, 2017 at 10:49 PM, Norberto Bensa
wrote:
> Hello Simos,
>
> 2017-04-13 10:44 GMT-03:00 Simos Xenitellis :
>> I got stuck with this issue (Ubuntu Desktop with NetworkManager) and
>> wrote about it at
>> https://www.mail-archive.com/lxc-users@lists.linuxcontainers.org/msg07060.html
>
Hello Simos,
2017-04-13 10:44 GMT-03:00 Simos Xenitellis :
> I got stuck with this issue (Ubuntu Desktop with NetworkManager) and
> wrote about it at
> https://www.mail-archive.com/lxc-users@lists.linuxcontainers.org/msg07060.html
For me, that doesn't work anymore with 17.04
I tried a lot of con
I got stuck with this issue (Ubuntu Desktop with NetworkManager) and
wrote about it at
https://www.mail-archive.com/lxc-users@lists.linuxcontainers.org/msg07060.html
I do not have a fresh Ubuntu machine handy; doesn't "lxd init"
populate automatically
the appropriate directory (whether it is for N
I found that in the 17.04 server edition it's enough to:
$ sudo apt-get install dnsmasq
$ sudoedit /etc/dnsmasq.d-available/lxc
add the following lines:
server=/lxc/10.0.3.1
server=/3.0.10.in-addr.arpa/10.0.3.1
$ sudoedit /etc/default/lxc-net
uncomment LXC_DOMAIN="lxc"
But, in the desktop ve
On Wed, Mar 29, 2017 at 12:59:15AM -0300, Norberto Bensa wrote:
> 2017-03-29 0:29 GMT-03:00 Serge E. Hallyn :
> > On Wed, Mar 29, 2017 at 12:16:29AM -0300, Norberto Bensa wrote:
> >> Hello list!
> >>
> >> In previous versions of Ubuntu I had lxc domain name resolution
> >> working, but it's broken
2017-03-29 0:29 GMT-03:00 Serge E. Hallyn :
> On Wed, Mar 29, 2017 at 12:16:29AM -0300, Norberto Bensa wrote:
>> Hello list!
>>
>> In previous versions of Ubuntu I had lxc domain name resolution
>> working, but it's broken for me in 17.04.
>
> https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-ne
On Wed, Mar 29, 2017 at 12:16:29AM -0300, Norberto Bensa wrote:
> Hello list!
>
> In previous versions of Ubuntu I had lxc domain name resolution
> working, but it's broken for me in 17.04.
>
> Name resolution inside the containers work:
>
> ubuntu@consulta:~⟫ ping fox
> PING fox.lxc (10.0.1.114
Hello list!
In previous versions of Ubuntu I had lxc domain name resolution
working, but it's broken for me in 17.04.
Name resolution inside the containers work:
ubuntu@consulta:~⟫ ping fox
PING fox.lxc (10.0.1.114) 56(84) bytes of data.
64 bytes from fox.lxc (10.0.1.114): icmp_seq=1 ttl=64 time
17 matches
Mail list logo
