Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #62048
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| 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) |
| Date | 2018-09-08 21:40 +0200 |
| Message-ID | <wvRfj-Fy-3@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <wvkjn-6m9-7@gated-at.bofh.it> <wvk01-6g8-7@gated-at.bofh.it> <wvpsJ-Q4-1@gated-at.bofh.it> <wvk01-6g8-7@gated-at.bofh.it> <wvpsJ-Q4-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
Control: affects -1 + lxc systemd On Fri, Sep 07, 2018 at 09:54:30PM +0800, johnw wrote: > 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 It for instance might affect as well systemd units, which use PrivateDevices=, e.g. see https://github.com/systemd/systemd/pull/9483 . TTBOMK, the change is beeing discussed to be reverted, https://lore.kernel.org/lkml/20180705155120.22102-1-christian@brauner.io/ Regards, Salvatore
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#908192: linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start John Wong <johnw.mail@gmail.com> - 2018-09-07 10:10 +0200
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) johnw <johnw.mail@gmail.com> - 2018-09-07 10:30 +0200
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) johnw <johnw.mail@gmail.com> - 2018-09-07 16:00 +0200
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) Salvatore Bonaccorso <carnil@debian.org> - 2018-09-08 21:40 +0200
Processed: Re: 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) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-09-08 21:40 +0200
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) Salvatore Bonaccorso <carnil@debian.org> - 2018-09-22 21:30 +0200
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) Christian Brauner <christian@brauner.io> - 2018-10-09 02:10 +0200
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) Salvatore Bonaccorso <carnil@debian.org> - 2018-10-13 22:40 +0200
Processed (with 1 error): Re: 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) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-10-13 22:40 +0200
Bug#908192: linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start Pierre-Elliott Bécue <peb@debian.org> - 2019-01-11 00:10 +0100
Bug#908192: marked as done (linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-01-11 04:00 +0100
Bug#908192: linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start Pierre-Elliott Bécue <peb@debian.org> - 2019-01-11 04:30 +0100
csiph-web