End of LXD support on this forum

End of LXD support

It has now been over a year since Canonical fully took over the LXD project.
On top of that change, Canonical’s decision to re-license LXD prevents any of us developers from looking at their current source code without risking legal issues.

We understand that it may sometimes be difficult to get in touch with the Canonical team and get adequate support on LXD.
But Incus has now been around for close to a year, is easy to migrate to and is fully supported by this community.

Moving forward, we will be automatically closing all new topics referring to LXD or its components.

4 Likes

Does this also apply to old posts from the LXD category that popup from time to time? Resurrecting old threads seems like a simple way to side step the new policy.

Those are a bit tricky because occasionally it’s someone reviving a thread because they hit the same thing on Incus. But if we see it used to get LXD support, then we’ll just close the topic.

Or you could just make all LXD threads read-only? Then if someone has a similar issue, they can start an incus thread and link to the LXD one if it’s relevant.