• [RFC] News item: LXD to lose access for its image server

    From Joonas Niilola@21:1/5 to All on Mon Dec 25 19:10:02 2023
    To: pr@gentoo.org

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------0UDgCeUYh1tdWJjyzbyKN43x
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    ### 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.

    --------------0UDgCeUYh1tdWJjyzbyKN43x--

    -----BEGIN PGP SIGNATURE-----

    iQGTBAEBCgB9FiEEltRJ9L6XRmDQCngHc4OUK43AaWIFAmWJw41fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDk2 RDQ0OUY0QkU5NzQ2NjBEMDBBNzgwNzczODM5NDJCOERDMDY5NjIACgkQc4OUK43A aWLcUggAg109/b7ocu/YdQHEpLvBMZ4G4XlHQQ3EaGNxZ4Si8eCrQ+h16QbBPMdk 8XC1pcKhnt7dXLgFfvGgmxAxfPcStp980xAg/ugP9JC98goQ+5GPDzw34fXh7KWD BveOXt6Dbtl1ydKyorwVSKZVWVUuDjDj9lCOwROJ2Y9MzjcT6cail3CY8ibR3YPe /yUqVLEu5JYy10T2+igaeZfxWnT8Ovhy6XJ3dCSOHbie9+9Pj9OrX2rKAc3xWdbr XwOI9eipx5HObUaG2HBcXWgLay55+hoa52ppTBMB77yNXyHnZldfLmdOatY56q7j BoBED4EsnDvCORFVPkTohx2lfKT+eg==
    =pNIY
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)