Earlier quoted context omitted.
What is Lennart doing at Microsoft?
AFAIK WSL
More specifically, getting systemd to work on WSL2, but he still has the same collection of projects, including UKI and so on.
LXD is now under Canonical
151–160 of 224 posts
Re: LXD is now under Canonical
#152Earlier quoted context omitted.
Yeah I'm setting up a Debian 12 Bookworm machine right now after ~13 years of being an Ubuntu user So far it's very snappy! My Ubuntu 18.04 machine somehow "rotted" in ways that previous installs didn't -- everything became slow and janky, sorta like Windows And I specifically installed 18.04 in 2021, to avoid Snaps But now it looks like Debian will work great
I'm in literally the same boat, on Debian now because of snaps. Their other homegrown stuff were mostly out of the way, like Unity or upstart, but snap was just really annoying with how it's integrated into the system.
On OpenSuSE Tumbleweed now because of Snap, rolling releases, best of class KDE support and pretty good testing of packages.
Re: LXD is now under Canonical
#153Earlier quoted context omitted.
It was like 15 years ago, but I though Canonical threw some red flags when they had that terrible ubuntu GUI update to have a ribbon. Completely unnecessary, 100% visual, and made everything worse. I bailed from them shortly after that, even with the option to use other GUIs. As Linux desktop has matured, it hasnt been necessary to go back to Ubuntu. I imagine most of Canonical's power comes from users who don't try…
> that terrible ubuntu GUI update to have a ribbon. Which one was that? No version of Ubuntu I've ever seen has ribbons. This is one of the reasons I like it. Do you mean when they switched from Unity to GNOME?
Yeah that sounds right. I can't quite remember the details because it has been 15 years and I loved trying different distros in general. I wasn't tied to the Ubuntu platform.
I suppose if I'm tied to anything, its the Debian branch of distros.
Re: LXD is now under Canonical
#154Earlier quoted context omitted.
It is really sad that more people aren't aware of LXD, because it is a really good solution of a number of projects and it's really well done. On Snap... Even if you like Snaps packages, I can't imagine that you'd feel like it's a good choice for LXD. For a browser or email client, sure it's a solution, I suppose, but for thing like LXD it just adds an entire level over complexity that doesn't help. I'd go so far at…
`snap refresh --hold` will hold updates indefinitely https://snapcraft.io/docs/keeping-snaps-up-to-date#heading--...
That's at least a comfort that they finally implemented that, I haven't used Snap in the past year, so I missed that.
Re: LXD is now under Canonical
#155Earlier quoted context omitted.
It is really sad that more people aren't aware of LXD, because it is a really good solution of a number of projects and it's really well done. On Snap... Even if you like Snaps packages, I can't imagine that you'd feel like it's a good choice for LXD. For a browser or email client, sure it's a solution, I suppose, but for thing like LXD it just adds an entire level over complexity that doesn't help. I'd go so far at…
It's also annoyingly opinionated in stupid ways. There's no supported way, for example, to adjust which services are enabled or not, and especially there's no concept of 'started but not autostarted', which can be important on a server (it's also obnoxious on the desktop as well, since it seems like a lot of the results for trying to fix this is people saying 'how do I stop snap slowing down boot').
According to the documentation services can be enabled and disabled. They can also be started but not enabled to automatically start.
Re: LXD is now under Canonical
#156Earlier quoted context omitted.
`snap refresh --hold` will hold updates indefinitely https://snapcraft.io/docs/keeping-snaps-up-to-date#heading--...
I suspect the thing people find offensive is that this is not the default
It seems like it was only introduced in December, so I can see why they haven't made it the default. It would be rather surprising to have run a Snap package for the past six years and then suddenly have it stop updating.
Re: LXD is now under Canonical
#157Stéphane Graber's work is fantastic and LXD had a lot of potential. But Canonical managed to drive me away from it with that abomination called Snap and its auto updates that could bring down a cluster without warning.
unfortunately, the same for me. I would really like to spin up some lxd container on fedora but not with snap.
Re: LXD is now under Canonical
#158Earlier quoted context omitted.
I'm in literally the same boat, on Debian now because of snaps. Their other homegrown stuff were mostly out of the way, like Unity or upstart, but snap was just really annoying with how it's integrated into the system.
On OpenSuSE Tumbleweed now because of Snap, rolling releases, best of class KDE support and pretty good testing of packages.
Sounds attractive. I quickly read up on it, and apparently gaming is also not a problem. Next time I install Linux, I'll give it a whirl!
Re: LXD is now under Canonical
#159Earlier quoted context omitted.
I gotta try multi node k8s setup for lxd
There are a few settings to figure out before LXD containers can host K8s. It's mainly about running the LXD containers in privileged mode. I have the settings written down somewhere. I think I should publish it somewhere, considering the expressed interest in it.
might be previleged , nested , and one other setting i don't remmber.
Re: LXD is now under Canonical
#160Earlier quoted context omitted.
> What's peoples aversion to snaps in the thread? In my case, because it's being forced and replacing applications that worked out of the box with applications with issues. Firefox, for example. After it became a snap, you'll see a message telling you to close Firefox so it could update itself (?) but simply closing it is not enough and, last time I checked, it looked like you had to run some command line to solve it…
Eh Firefox probably isnt the best example due to security being so important. Something like an IDE is a better example since its not much of an attack vector.
You mean Firefox is a good fit for a snap due to security reasons? In that case they should've made the experience seamless, and provide the same functionality you get when using Firefox from the deb or the tarball, before pushing it like that.
Because otherwise, the result is people pissed off with that change.