Initial release of Incus, the LXD community fork (discuss.linuxcontainers.org) 16 points by ropyeett 2y ago ↗ HN
[–] ropyeett 2y ago ↗ Incus 0.1 has been released, setting things up for this community, Canonical-less fork of LXD. [–] beanjuiceII 2y ago ↗ why is a canonical-less fork needed again? [–] arp242 2y ago ↗ There are a few different variants of LXD and they wanted to create a canonical version.I'll get my coat. [–] lproven 2y ago ↗ I see what you did there. :-D [–] upon_drumhead 2y ago ↗ I would presume it's to keep it from being locked into Ubuntu? [–] ropyeett 2y ago ↗ LXD was run as part of Linux Containers with maintainers from a few different companies and hundreds of external contributors over the years.Then Canonical, who owned the trademark on it told the team that it wanted it moved in house and rebranded Canonical LXD.Shortly after, Stephane Graber, the project leader left Canonical.A few weeks later, Incus started as a community fork with all the original LXD maintainers joining in and the fork moving to Linux Containers.Incus feels like a more open protect, no focus on one distro or company, no shoving of a snap package down everyone's throat.Will see how things go.
[–] beanjuiceII 2y ago ↗ why is a canonical-less fork needed again? [–] arp242 2y ago ↗ There are a few different variants of LXD and they wanted to create a canonical version.I'll get my coat. [–] lproven 2y ago ↗ I see what you did there. :-D [–] upon_drumhead 2y ago ↗ I would presume it's to keep it from being locked into Ubuntu? [–] ropyeett 2y ago ↗ LXD was run as part of Linux Containers with maintainers from a few different companies and hundreds of external contributors over the years.Then Canonical, who owned the trademark on it told the team that it wanted it moved in house and rebranded Canonical LXD.Shortly after, Stephane Graber, the project leader left Canonical.A few weeks later, Incus started as a community fork with all the original LXD maintainers joining in and the fork moving to Linux Containers.Incus feels like a more open protect, no focus on one distro or company, no shoving of a snap package down everyone's throat.Will see how things go.
[–] arp242 2y ago ↗ There are a few different variants of LXD and they wanted to create a canonical version.I'll get my coat. [–] lproven 2y ago ↗ I see what you did there. :-D
[–] ropyeett 2y ago ↗ LXD was run as part of Linux Containers with maintainers from a few different companies and hundreds of external contributors over the years.Then Canonical, who owned the trademark on it told the team that it wanted it moved in house and rebranded Canonical LXD.Shortly after, Stephane Graber, the project leader left Canonical.A few weeks later, Incus started as a community fork with all the original LXD maintainers joining in and the fork moving to Linux Containers.Incus feels like a more open protect, no focus on one distro or company, no shoving of a snap package down everyone's throat.Will see how things go.
7 comments
[ 4.9 ms ] story [ 35.8 ms ] threadI'll get my coat.
Then Canonical, who owned the trademark on it told the team that it wanted it moved in house and rebranded Canonical LXD.
Shortly after, Stephane Graber, the project leader left Canonical.
A few weeks later, Incus started as a community fork with all the original LXD maintainers joining in and the fork moving to Linux Containers.
Incus feels like a more open protect, no focus on one distro or company, no shoving of a snap package down everyone's throat.
Will see how things go.
https://news.ycombinator.com/item?id=37799477