Selfhosted

40152 readers

482 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

262

Broadcom yanks ESXi Free version, effective immediately (kb.vmware.com)

submitted 9 months ago by kalpol@lemmy.world to c/selfhosted@lemmy.world

126 comments fedilink hide all child comments

I'd expected this but it still sucks.

you are viewing a single comment's thread
view the rest of the comments

[–] TCB13@lemmy.world 4 points 9 months ago* (last edited 9 months ago) (1 children)

So I’m kind of scared about the future of LXC and Incus. Do you have any more information about that?

Canonical decided to take LXD away from the Linux Containers initiative and "close it" by changing the license. Meanwhile most of the original team at Canonical that made both LXC and LXD into a real thing quit Canonical and are not working on Incus or somehow indirectly "on" the Linux Containers initiative.

no one else participating apart from Canonical devs.

Yes, because everyone is pushing code into Incus and the team at Canonical is now very, very small and missing the key people.

The future is bright and there's money to make things happen from multiple sources. When it comes to the move from LXD to Incus I specifically asked stgraber about what’s going to happen in the future to the current Debian LXD users and this was his answer:

We’ve been working pretty closely to Debian on this. I expect we’ll keep allowing Debian users of LXD 5.0.2 to interact with the image server either until trixie is released with Incus available OR a backport of Incus is made available in bookworm-backports, whichever happens first.

As you can see, even the LTS LXD version present on Debian 12 will work for a long time. Eventually everyone will move to Incus in Debian 13 and LXD will be history.

Update: here's an important part of the Incus release announcement:

The goal of Incus is to provide a fully community led alternative to Canonical’s LXD as well as providing an opportunity to correct some mistakes that were made during LXD’s development which couldn’t be corrected without breaking backward compatibility.

In addition to Aleksa, the initial set of maintainers for Incus will include Christian Brauner, Serge Hallyn, Stéphane Graber and Tycho Andersen, effectively including the entire team that once created LXD.

[–] msage@programming.dev 2 points 9 months ago

Excelent write-up, thank you very much. I'm going to invest my time to learning Incus!