Branch: refs/heads/stable-4.0
Home: https://github.com/lxc/lxc
Commit: 34a93d419082723da41d76dcfe38845b3d12f95c
https://github.com/lxc/lxc/commit/34a93d419082723da41d76dcfe38845b3d12f95c
Author: sirh3e <marvin.hu...@bluewin.ch>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M README.md
Log Message:
-----------
Changed Version from 2.*.* to 4.*.*
Signed-off-by: sirh3e <marvin.hu...@bluewin.ch>
Commit: 1058884aec865166633fcfb65931fa8a74170950
https://github.com/lxc/lxc/commit/1058884aec865166633fcfb65931fa8a74170950
Author: Motiejus Jakštys <motie...@jakstys.lt>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M config/init/common/lxc-net.in
Log Message:
-----------
make lxc-net hermetic w.r.t. existing dnsmasq config
lxc's dnsmasq will try to read system's dnsmasq if `--conf-file` is not
specified. This is likely not desirable, as lxc's dnsmasq should be
self-contained.
On my system the conflicting options are `--bind-interfaces` and
`--bind-dynamic`, since the same host is doing other DNS-y things
unrelated to lxc.
This is an incompatible change, since lxc's dnsmasq will stop honoring
system's `/etc/dnsmasq.conf`, and some systems may be relying on it.
Given that, I believe it should not depend on it by default, since
dnsmasq is lxc's implementation detail. However, if the user desires,
the old behavior could be brought back by setting
`LXC_DHCP_CONFILE=/etc/dnsmasq.conf` in `/etc/default/lxc-net`.
Signed-off-by: Motiejus Jakštys <motie...@jakstys.lt>
Compare: https://github.com/lxc/lxc/compare/952ab618268b...1058884aec86
_______________________________________________
lxc-devel mailing list
lxc-devel@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-devel
