Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lxc still being maintained? #7694

Open
n8v8R opened this issue Dec 16, 2018 · 22 comments

Comments

Projects
None yet
8 participants
@n8v8R
Copy link

commented Dec 16, 2018

@rmilecki Having looked at the package history and its current version 2.1.1 and compared to upstream version 3.0.3 with various bug fixes and security patches I am curious thus whether the package is still actively maintained?

@stintel

This comment has been minimized.

Copy link
Member

commented Dec 28, 2018

@ratkaj

This comment has been minimized.

Copy link
Contributor

commented Jan 3, 2019

Hi @n8v8R, @stintel,

yes it is. Trying to find the time to update for a while now, didn't think there was any interest.
I'll try to bump within a week.

@n8v8R

This comment has been minimized.

Copy link
Author

commented Jan 3, 2019

@ratkaj Thank you for the feedback and time/effort put into maintenance 👍

Probably the user base is rather small indeed considering the hardware requirements (external disk to avoid wearing the NAND, sufficient RAM and CPU power). But a few routers do match such requirements and perhaps more to come. Also the number of user interested in lxc might increase over time - currently it seems not be widely known.

@cshoredaniel

This comment has been minimized.

Copy link
Contributor

commented Jan 3, 2019

Also 2.1.1 is latest LTS

@cshoredaniel

This comment has been minimized.

Copy link
Contributor

commented Jan 3, 2019

And is in fact up-to-date for that branch

@n8v8R

This comment has been minimized.

Copy link
Author

commented Jan 3, 2019

@cshoredaniel https://discuss.linuxcontainers.org/t/lxc-3-0-3-has-been-released/3358

Support and upgrade

LXC 3.0.3 is supported until June 2023 and is our current LTS release, users are encouraged to update to the latest bugfix releases as they’re made available.

@cshoredaniel

This comment has been minimized.

Copy link
Contributor

commented Jan 3, 2019

Hmmm....I'm surprised, I must have misread the website (or it's not yet been updated).

@cshoredaniel

This comment has been minimized.

Copy link
Contributor

commented Jan 3, 2019

https://linuxcontainers.org/lxc/introduction/ gives the wrong impression -- 1.whatever and 2.whatever are the old LTS not the current LTS. Should file a bug with them to update the site to be more clear.

@alump

This comment has been minimized.

Copy link

commented Feb 10, 2019

2.1 never even was a LTS version? 2.0 was/is the LTS version before 3.0. 2.1 support has actually ended on September 2018 already.

@n8v8R

This comment has been minimized.

Copy link
Author

commented Feb 10, 2019

@alump https://discuss.linuxcontainers.org/t/lxc-2-1-has-been-released/487

Note that this isn’t a LTS release and we’ll therefore only be supporting LXC 2.1 for a year.

@cshoredaniel

This comment has been minimized.

Copy link
Contributor

commented Feb 10, 2019

Yeah their 'introduction' page really needs some love.

@n8v8R

This comment has been minimized.

Copy link
Author

commented Feb 10, 2019

The release history seems better documented here https://linuxcontainers.org/lxc/news/

But that aside what is happening (or going to happen) with the maintenance of LXC in OpenWRT?

@dangowrt

This comment has been minimized.

Copy link
Member

commented Feb 11, 2019

@n8v8R

This comment has been minimized.

Copy link
Author

commented Feb 12, 2019

One of many security patches missed in an unmaintained LXC package.

https://brauner.github.io/2019/02/12/privileged-containers.html

@AreYouLoco

This comment has been minimized.

Copy link

commented Feb 14, 2019

I am also looking for the upstream update of lxc package. I am interested in non-privilidged containers option.

@BKPepe

This comment has been minimized.

Copy link
Member

commented Mar 28, 2019

@ratkaj Is there anything new about this issue? Did you have time to look at it?

@n8v8R

This comment has been minimized.

Copy link
Author

commented Jun 4, 2019

Not sure who did the effort but just found

cat /usr/lib/opkg/info/lxc.control

Package: lxc
Version: 3.0.3-0.0
Depends: libc
Source: feeds/packages/utils/lxc
License: LGPL-2.1+ BSD-2-Clause GPL-2.0
Section: utils
Maintainer: Marko Ratkaj marko.ratkaj@sartura.hr
Architecture: arm_cortex-a9_vfpv3
Installed-Size: 104

@n8v8R n8v8R closed this Jun 4, 2019

@stintel

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

@n8v8R

This comment has been minimized.

Copy link
Author

commented Jun 4, 2019

@stintel just discovered that it originates from downstream TurrisOS

@AreYouLoco

This comment has been minimized.

Copy link

commented Jun 4, 2019

Great! I wonder if the update will go upstream so others can benefit from it.

@BKPepe BKPepe reopened this Jun 4, 2019

@BKPepe

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

Guys, we (as Turris guys) already said on the forum that we are working on it and we would like to upstream it. It's WIP and it requires some more changes before it can be upstreamed. You can check the issue, which is on Turris Gitlab.

@n8v8R: I would like to kindly ask you to avoid using words like downstream and so on. It will just confuse other users. Since Turris OS 4.x we are based on top of OpenWrt with patches and our feed. Some of it, it couldn't be upstream at all as it is CZ.NIC (if you prefer Turris) specific.

Our work is open source. If you are interested in helping us, you can. ;-) Patches are always welcome. You can even see that me and also others are working on sending patches to OpenWrt as much as we can.

Don't confuse the issue with offtopic as it is not related to the issue at all.

@cshoredaniel

This comment has been minimized.

Copy link
Contributor

commented Jun 5, 2019

@BKPepe Not sure why you take issue with downstream -- OpenWrt is upstream therefore you are downstream. If seen the terms used in other projects (e.g. in reference to Ubuntu derivatives as downstream). In open source it is understood downstream is not an exactly replica of upstream, and has unique things/target audience/situation that may not be applicable to upstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.