3 ms·
Systemd-nspawn or LXD/Incus are also alternatives. LXD user experience is pretty good.
by loloquwowndueo 3y ago
Systemd-nspawn or LXD/Incus are also alternatives. LXD user experience is pretty good.
- leosanchez 3y agoI liked LXD from the limited time I spent on it. Do you know any resources to learn it a bit more in depth ?
- Grimburger 3y agoReading this makes me concerned as someone who loves LXD, because when you reflect on it there's not really that much for newcomers besides some blog posts or a "fail and ask on the forums" model which clearly isn't optimal for some learning styles. It's a probably a misstep by the linux containers ecosystem, I do hope Incus can improve on this.
- goku12 3y agoLXD official online documentation (now hosted by Canonical) is the sole resource I needed to set it up and use it. The CLI concepts and commands are designed well enough and is intuitive. The only outside resource I had to read was for some privileged containers running K8s inside.
- bongobingo1 3y agoI feel like LXD shot them selves in the foot with terminology. When ever I got interested I would get confused between LXC and LXD and lxc the command (part of LXD) and lxd the command. Now its even muddier with Canonical ... taking back (?) LXD. Throw in the alternative vision (LX* containers are more like persistent VMs than ephemeral containers) and a lack of `<container-engine> pull app` and all that entails re: DevX and DeployX, it always felt like a mountain to get going.
- goku12 3y agoThe team behind Incus (the fork of LXD) is working on that problem. They have decided on unambiguous names and have even rearranged some commands to make it consistent and clear.
- rascul 3y ago> `<container-engine> pull app` Is quite doable with lxc. An application container can be built and shared. It doesn't appear to be typically done, though.