Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #205502 > unrolled thread
| Started by | Claudio Kuenzler <ck@claudiokuenzler.com> |
|---|---|
| First post | 2019-02-19 09:00 +0100 |
| Last post | 2019-02-19 15:40 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.user
Status of LXC in Stretch? Claudio Kuenzler <ck@claudiokuenzler.com> - 2019-02-19 09:00 +0100
Re: Status of LXC in Stretch? Jonathan Dowland <jmtd@debian.org> - 2019-02-19 15:40 +0100
| From | Claudio Kuenzler <ck@claudiokuenzler.com> |
|---|---|
| Date | 2019-02-19 09:00 +0100 |
| Subject | Status of LXC in Stretch? |
| Message-ID | <xt8tP-2kk-3@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Dear all, LXC maintainers,
It seems that there hasn't been much going on concerning the LXC package(s)
in Debian 9 Stretch. The version is stuck at 2.0.7 without any patches
backported since Jan 2018. Yet there are known (important) bugs which break
LXC on Stretch.
For example when using cgroup resource limits, bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888647 occurs, which at
the end is a bug in the used libpam-cgfs package.
Even in backports there is the following note in the changelog of the lxcfs
package:
lxcfs (2.0.8-1~bpo9+1) stretch-backports; urgency=medium
* Team upload
* Rebuild for stretch-backports.
* This backport release is an alternative to 2.0.7-1 that has a couple of
issues, and shouldn't have reached stable.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867619 for more
intel.
-- Pierre-Elliott Bécue <peb@debian.org> Sat, 17 Nov 2018 09:01:07 +0100
In bug #888647 as well as in a discussion on linuxcontainers.org (
https://discuss.linuxcontainers.org/t/failed-creating-cgroups/272/10) a
possible solution is to remove the Debian package of libpam-cgfs and
instead install the Ubuntu package. Really?!
Although this workaround seems to work for some, it doesn't work for others
including the author of the last comment in bug #888647.
Meanwhile LXC 2.0.9 is out since October 2017 (yes, 2017). Instead of
keeping a bugged 2.0.7, wouldn't it be better to include the latest
upstream version of the 2.0 LTS branch?
Note: LXC itself works fine for privileged containers _without_ resource
lmits. But as soon as resource limits are used, this bug comes in place and
breaks LXC.
What's the current status with LXC and its related packages in Debian
Stretch? Can we expect a new upstream release, a bugfix or a new version
(3.0 LTS) made available in backports?
Thanks in advance for letting us know.
[toc] | [next] | [standalone]
| From | Jonathan Dowland <jmtd@debian.org> |
|---|---|
| Date | 2019-02-19 15:40 +0100 |
| Message-ID | <xteIV-61J-5@gated-at.bofh.it> |
| In reply to | #205502 |
Hi, On Tue, Feb 19, 2019 at 08:50:01AM +0100, Claudio Kuenzler wrote: >It seems that there hasn't been much going on concerning the LXC package(s) >in Debian 9 Stretch. The version is stuck at 2.0.7 without any patches >backported since Jan 2018. Yet there are known (important) bugs which break >LXC on Stretch. Ultimately, I think the LXC maintainers are under-resourced; there aren't enough people/hours for it. But Stretch being the current release, I would not expect to see the package update much, except for security issues or *major* bugs. #888647 that you cite, for example, is currently only categorized as "normal" severity. >Meanwhile LXC 2.0.9 is out since October 2017 (yes, 2017). Instead of >keeping a bugged 2.0.7, wouldn't it be better to include the latest >upstream version of the 2.0 LTS branch? Not post-Stretch release, no; that's not how we do things I'm afraid. Unfortunately 2.0.9 came out *after* Stretch, by a few months. >What's the current status with LXC and its related packages in Debian >Stretch? You've pretty much summed it up. > Can we expect a new upstream release, a bugfix or a new version >(3.0 LTS) made available in backports? I can't speak for the LXC maintainers, but we as a project are about to enter freeze for the next Debian release. The version of LXC slated for that is 3.x series. I suspect (but again, can only speculate) that the maintainers are likely going to prioritize getting the next release ready over updating the backport for the soon-to-be-obsolete current stable release. Volunteers are free to work on whatever they want, of course. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland ⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net ⠈⠳⣄⠀⠀⠀⠀ Please do not CC me, I am subscribed to the list.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web