Hello everyone, I was using LXC — unprivileged — containers for my only two containers. I don't know how much but about a year, perhaps. Meanwhile, reading announcements of Incus following their GitHub release notifications. I was just interested. With v0.5 release, I jumped in, gave it a try and yeah!! it was simpler than LXC itself. Exactly opposite to my guessing. So far, everything was going well. Two little problems that I reported, one has to be documented in archwiki and the other will be fixed in 0.7. Since I dodged LXD directly from LXC to Incus. I want to know what's the difference between their _interfaces_. Am I missing anything from LXD in Incus? -- Best Regards, Abraham Sent with Tutanota; https://tuta.com
Hello,
So far, everything was going well. Two little problems that I reported, one has to be documented in archwiki and the other will be fixed in 0.7.
Link? Pointless mentioning them unless you say what the issues were, or link to where you reported them.
Since I dodged LXD directly from LXC to Incus. I want to know what's the difference between their _interfaces_. Am I missing anything from LXD in Incus?
Almost seemless transfer between LXD and Incus, and they work the same, just substitute lxd with incus. LXD is no longer practical to use as it has been dropped from linuxcontainers repository and thus you can't pull container images from linuxcontainers using LXD anymore. Also there is now licencing disputes between linux containers and Canonical. Canonical relicenced LXD under AGPLv3, and to avoid dual licencing Incus will not include future LXD code, which is diverting paths between both utilities. Incus remains permissively licenced under Apache. [1][2] (second link appears to be down?) Hope this helps. Take care, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@icebound.dev [1] https://news.ycombinator.com/item?id=38618696 [2] https://discuss.linuxcontainers.org/t/lxd-has-been-re-licensed-and-is-now-un...
Link? Pointless …
Yeah, sorry, that was pointless.
(second link appears to be down?)
No, it was accessible.
… they work the same …
Good. Thanks for feedback.
… seemless transfer between LXD and Incus …
Didn't have LXD. Manually replicated my Alpine containers in Incus. Took me a few hours (two or three), probably the same amount to spend finding a way to transfer them in some automatic way.
LXD is no longer practical to use as it has been dropped from linuxcontainers repository …
They will probably establish their own image servers.
Canonical …
(coughs...Microsoft of FOSS world...coughs)
AGPLv3
Plus Canonical's CLA -- Best Regards, Abraham Sent with Tutanota; https://tuta.com
Hello,
No, it was accessible.
Weird I couldn't access it at the time of writing my previous email, the A record returned blank with a SERVFAIL. Doesn't matter, it works now for me too :)
Didn't have LXD. Manually replicated my Alpine containers in Incus. Took me a few hours (two or three), probably the same amount to spend finding a way to transfer them in some automatic way.
There is a tool to do this for you, its lxc-to-incus and it imports lxc containers to incus, it is within incus-tools. [1] You could have used this tool and saved yourself a lot of time, but hey you got there in the end :D Take care, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@icebound.dev [1] https://archlinux.org/packages/extra/x86_64/incus-tools/
Probably, an off-topic noise of course. But wanted it to be on thread rather than a private email. I always appreciate your writes. The time, effort, and responsiveness that you put to write your letters in Arch mailing lists. Not everyone is as generous or capable (me also added to the list) in spending them for free. -- Best Regards, Abraham Sent with Tutanota; https://tuta.com
participants (2)
-
Abraham S.A.H.
-
Polarian