- cross-posted to:
- linux@programming.dev
- containers@lemmy.world
- technews@radiation.party
- cross-posted to:
- linux@programming.dev
- containers@lemmy.world
- technews@radiation.party
Interesting move by Canonical. Wonder if this is related to the new GUI for LXD that Canonical released recently? Or maybe they want to bring more projects in-house after the RHEL shakeup?
You must log in or register to comment.
How do you notice that you are not really awake yet? By thinking for several minutes about what LXD has to do with containers and then realising that you yourself had LXDE in mind.
huh, was it not before? i thought the entire lx* space was canonical’s thing
Was developed by Canonical, but under the Linux Containers umbrella.
Used it once or twice then stopped, prefer raw lxc or even just manually creating namespaces if I want control.
Never quite understood the point, the additional polish seemed fairly minimal from a utility pov.
They should take over proxmox or something, give themselves a complete story.
They should take over proxmox
You shut your whore mouth.
I just switched off of proxmox back to vanilla lxc and virt-manager, I’m feeling brave right now :)
Removed by mod
Oh, bullshit. The minimal interface that Ubuntu offers isn’t even a pimple on the Proxmox front end, and doesn’t touch the filesystem, clustering abilities and backup solution that’s the equivalent of Veeam IMO.
Removed by mod
I haven’t been following, but that’s actually good to hear, proxmox needs a better ui.
LXD, I suppose for the migration, but for any more complex orchestration I think you’ve moving to k8s or something more serious, LXD just has an odd “not enough but too much” feature set for me, I like things either push-button, or let me do it, this is kind of both.
Removed by mod
Ah, ok, understood then, it didn’t fit my use-case or workflow, it works for others, my bad, appreciate the correction!
Removed by mod
I do that with lxd, but I have written ansible playbooks (almost like dockerfile? ) to automate the lxd containers. You could probably write some automation for scaling as well, but not something I’ve done, I have just opted for high availability with ceph & keepalived. Whatever works for your use case :) I do use some docker, but this is still nested inside lxd…
Removed by mod
I don’t know if I want a project as cool as Proxmox owned by the “you will use snap and you will like it” Canonical
RIP LXD
I wonder if this means LXC (which seems neglected lately) and LXD will soon be maintained by different people.
