public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joonas Niilola <juippis@gentoo.org>
To: gentoo-dev@lists.gentoo.org, pr@gentoo.org
Subject: [gentoo-dev] [RFC] News item: LXD to lose access for its image server
Date: Mon, 25 Dec 2023 20:01:49 +0200	[thread overview]
Message-ID: <a5f49dbb-9888-4531-9ace-c6fe28c1e5f9@gentoo.org> (raw)


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

### Notes: Tried to keep this news item as concise as possible,
### more information in #920527.


Title: LXD to lose access for its image server
Author: Joonas Niilola <juippis@gentoo.org>
Posted: 2023-12-28
Revision: 1
News-Item-Format: 2.0
Display-If-Installed: app-containers/lxd

Earlier this year Canonical took their LXD project from
community-hosted LinuxContainers under Canonical's own management.
While doing so, they removed management access from non-Canonical
employees, along with other things. This caused LXD to be forked and so
Incus was born. Incus would pull updates from upstream LXD to stay
compatible.

Recently LXD was re-licensed so Incus can't benefit from its code
anymore. Therefore Incus will become a truly independent project.

However it is LinuxContainers community that still hosts most LXD
images for free, for Incus and LXD. With them unable to benefit or use
LXD anymore, LinuxContainers have decided to stop building and hosting
LXD images. They will start limiting access immediately in 2024 for
non-LTS users which is LXD >=5.18, or "unstable" in Gentoo. LTS LXD, or
"stable" (5.0) in Gentoo will be allowed to pull images until May (an
estimate), or until Incus LTS will be released. Times are subject to
change.

What can you do?
================

1: Switch to Incus.
2: Deploy your own image server.
3: Wait and see what Canonical does.

For unstable users the matter is rather urgent, while stable users
have the luxury of waiting. Note that a downgrade from unstable to
stable is not possible due to database schemas.

Please follow or take a look at Gentoo bug #920527 with more
information about this situation, and updates e.g. for timetables.

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

             reply	other threads:[~2023-12-25 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-25 18:01 Joonas Niilola [this message]
2023-12-26  5:29 ` [gentoo-dev] Re: [RFC] News item: LXD to lose access for its image server Oskari Pirhonen

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=a5f49dbb-9888-4531-9ace-c6fe28c1e5f9@gentoo.org \
    --to=juippis@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=pr@gentoo.org \
    /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