Forum for Linux distributions to discuss problems and share PSAs
 help / color / mirror / Atom feed
From: Joonas Niilola <juippis@gentoo.org>
To: distributions@lists.linux.dev
Subject: LXD going to lose access to its image server
Date: Sat, 23 Dec 2023 08:18:03 +0200	[thread overview]
Message-ID: <a0db38ec-347d-4b26-97a2-e77d679f05fe@gentoo.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1909 bytes --]

Hey,

short gist is: Earlier this year Canonical moved the LXD project from
community-hosted LinuxContainers under Canonical's management. They
removed administrative access from non-Canonical employees and
introduced Canonical's CLA on all future contributors. Community didn't
like this, so they forked LXD and so Incus was born. Incus would pull
code from upstream LXD to stay compatible.

Now recently Canonical re-licensed LXD so that Incus couldn't pull code
from them anymore. Therefore Incus will become a fully independent project.

However it is LinuxContainers that builds and hosts nearly all LXD &
Incus container & VM images in https://images.linuxcontainers.org/ -
note that sites such as https://uk.lxd.images.canonical.com/ are just
mirroring the linuxcontainers.org one. Canonical only builds and hosts
their own Ubuntu images.

Because LinuxContainers community can't lean on to LXD, they've decided
not to build and publish LXD images anymore. Non-LTS LXD will gradually
start losing access to these images immediately in 2024, while LTS LXD
is allowed until ~April-May of 2024 to have a fair chance migrating into
Incus LTS, which is expected to be out in April 2024.

At the time of writing it's unclear what Canonical will do. Are they
going to start offering variety of distributions, or just focus on
Ubuntu? Either way this will most likely require actions from downstream
packages.

I've written a more-detailed, Gentoo-focused summary with current
timetables and "what can you do" actions to:
https://bugs.gentoo.org/920527

but basically:
 1: move to incus,
 2: host your own image server,
 3: wait and see what Canonical does.

Follow upstream announcement here:
https://discuss.linuxcontainers.org/t/important-notice-for-lxd-users-image-server/18479

Canonical's discussion forums:
https://discourse.ubuntu.com/c/lxd/126

-- juippis

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

                 reply	other threads:[~2023-12-23  6:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a0db38ec-347d-4b26-97a2-e77d679f05fe@gentoo.org \
    --to=juippis@gentoo.org \
    --cc=distributions@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).