3 ms·
I 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
by bongobingo1 3y ago
I 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.