On Mon, Nov 2, 2015 at 10:25 AM, Fajar A. Nugraha <[email protected]> wrote:
> On Sat, Oct 31, 2015 at 11:10 AM, MegaBrutal <[email protected]> wrote: > >> 2015-10-31 1:16 GMT+01:00 Andrey Repin <[email protected]>: >> > >> > Greetings, MegaBrutal! >> > >> > > I reported a bug for Ubuntu on Launchpad, which is related to LXC: >> > > https://bugs.launchpad.net/bugs/1511875 >> > >> > > I can't tell whether LXC or the Ubuntu release upgrader script is >> > > responsible for the described phenomenon. >> > >> > Did you install the new kernel on the host first? >> > >> >> The host is running with kernel 3.19.0-30-generic. (It's still Vivid, >> because thanks to completely unrelated bug #1509717, I must hold back >> upgrading the host.) However, if you want me to test with newer >> kernels, I can do it in KVM. Is it OK if I just test with the Wily >> kernel, or do you want me to try the latest vanilla kernel? >> > > > Since 16.04 is not even alpha yet, I doubt your bug report will be a > priority. I recommend you test again after first alpha is released. > > FWIW, I can upgrade succesfully with apt-get. This is with fully up-to-date wily packages (including kernel and lxc. lxc is from wily repository, not from ppa). "do-release-upgrade -d" failed for me due to a problem with friendly-recovery (which do-release-upgrade insists on installing, even when it was not installed before) that runs grub-probe, which fails inside the container. However when doing it manually, it works (and it does NOT install friendly-recovery in the upgrade process) : - create /etc/apt/sources.list.d/xenial.list with appropriate content - apt-get update - apt-get install apt dpkg - apt-get dist-upgrade In both cases, I do NOT get the hang you mentioned in the bug report. So you might want to try with a fresh system, or at least a fully up-to-date packages. -- Fajar
_______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
