Bug#908192: Acknowledgement (linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start)

To: 908192@bugs.debian.org
Subject: Bug#908192: Acknowledgement (linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start)
From: johnw <johnw.mail@gmail.com>
Date: Fri, 07 Sep 2018 21:54:30 +0800
Message-id: <[🔎] 68e4094a672772a891b3be52c6d3e0f1@gmail.com>
Reply-to: johnw <johnw.mail@gmail.com>, 908192@bugs.debian.org
In-reply-to: <handler.908192.B.153630762130524.ack@bugs.debian.org>
References: <[🔎] 153630761841.3845.3054759475313484066.reportbug@kvm102> <handler.908192.B.153630762130524.ack@bugs.debian.org> <[🔎] 153630761841.3845.3054759475313484066.reportbug@kvm102>

I can start privileged LXC containers with 4.18 kernel,
Only can not start unprivileged LXC containers with 4.18 kernel.

Maybe the problem is lxc, not the kernel,

https://lists.linuxfoundation.org/pipermail/containers/2018-June/039174.html

--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC

Reply to:

Follow-Ups:
- Bug#908192: Acknowledgement (linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start)
  - From: Salvatore Bonaccorso <carnil@debian.org>

References:
- Bug#908192: linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start
  - From: John Wong <johnw.mail@gmail.com>

Prev by Date: Bug#908196: linux-image-4.9.0-8-armmp: Please set CONFIG_LEDS_PCA963X=m
Next by Date: Bug#907175: 4.9.0-8-686-pae swapon failed invalid argument
Previous by thread: Bug#908192: Acknowledgement (linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start)
Next by thread: Bug#908192: Acknowledgement (linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start)
Index(es):
- Date
- Thread