On Tue, Apr 28, 2015 at 12:39 PM, Neil Williams <[email protected]> wrote: > On Tue, 28 Apr 2015 11:30:33 +0100 > Luke Kenneth Casson Leighton <[email protected]> wrote: > >> On Tue, Apr 28, 2015 at 9:07 AM, Neil Williams <[email protected]> >> wrote: >> >> > Chroot tests suffer from limitations with daemons (changed port >> > numbers if the same daemon is running outside etc.) and are subject >> > to whatever the running kernel can offer. >> >> has anyone considered modifying any automated chroot-based systems to >> use lxc? > > There hasn't been any work on lxc in LAVA at least. It's been mentioned > and some work has been planned but it's not scoped yet and there is > insufficient reason / insufficient resources to push for it.
ack. >> using lxc would solve the limitation that you describe, neil, about >> daemons having to change port numbers. the only thing you can't do is >> test kernel-related stuff (udev-related) with lxc. > > Kernel testing is the main objective of LAVA testing currently, so when > chroot isn't enough, a complete test as a virtual machine or a new > deployment is the main go-to. makes sense. esp. as a full VM - if you have to have it for one reason or another - makes the use of lxc unnecessary / redundant, so i see the sense in not prioritising it. ok i go back to sleep now :) l. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/capweedxoycjcwfw-pmfjvccstraw2ni9fej0zj7jv5x8l6r...@mail.gmail.com
