openSUSE MicroOS: Painless Containerized Workflows for Lazy Developers
ฝัง
- เผยแพร่เมื่อ 2 ต.ค. 2024
- ... or so they say? For this video I'll pretend to be a lazy developer and dive into the guts of this rising immutable Linux distro to see what's changed since the test drive last year!
20:47 - you don't need to reboot when disabling stuff, but you do need to include the '--now' parameter to your systemctl command to let it know you wish to disable it now, not on next boot
Thanks for sharing!
It's nice Distrobox is pre-installed now. Just a few months ago, it wasn't.
Very nice - wish Silverblue did it too!
Nice one! Have used microOS KDE for a week irl, it worked very well. The automatic reboot can be turned off in Discover and probably also in the Gnome Software store. The system can quietly update in the background, and upon reboot all is updated. Very convenient. Have to say though I generally turn off my computer at night or when leaving. Keep them coming!
Thanks for sharing!
Nice overview! I was considering installing its KDE spin on one machine over Kinoite for some of its saner (in my opinion) defaults, so this came just in time and it was very helpful!
Do you know if they plan to enable ZRAM by default in the future?
Good to hear!
Haven't read anything about any ZRAM plans yet, but I certainly hope they will. Thanks for watching!
I see, I did a little digging and according to a discussion and a related issue on Bugzilla it seems they don't currently find it to be a very good idea, it's unfortunate because who raised the issue communicated the reasoning behind it kind of poorly so in turn we didn't get a clear explanation as to why it would be a wrong decision, I think a good middle ground would have been a toggle in the installation process so that each user can decide based on their use case.
Seeing that they have setup a script that the user would have to run, as of now, after installation, it wouldn't be that far away, but it's good that the option is there in some form at least
Good to know, thanks for sharing here!
Stephen your awesome thank-you, your bald head lower left during is brilliant. Dude do more micro os lectures. Super thanks.
Keeping a sharp eye on MicroOS!
Sounds painful. What's up with, add pkg = reboot, add pkg = reboot, add pkg = reboot...
Without doing anything crazy is there an accepted method of using a Startup script to install all of your flathub packages (like you did in Fedora Silverblue) or like a Nix configuration file?
BTW - Thank you - Really nice you taking us through your process... A very through video.
Would I be able to use Distrobox to spin up a Windows instance via docker or whatever ?
Hi, I believe the target audience here is those who already know all the packages they need to install (all at once, single reboot) instead of piecemeal. This distro strikes me as "deploy and forget" and not a good fit for tinkering. Regular Tumbleweed might be better for a more traditional Linux experience. The flathub packages portion of the Fedora SB script should work here just fine unaltered.
Distrobox is meant for running other Linux distro instances in containers. For Windows 11, I currently use QEMU/KVM with great results and automatic USB pass through!
Good luck and thanks for your support! :)
genial muchas gracias por el video, todo un maestro..
🙏
Thank you very much for another great, informative video, looking beyond the mainstream!
Our pleasure!
I was looking at using microos on my dell poweredge servwr, but I am not very happy about the update frequency of tumbleweed for a server.
I cant wait for slowroll to be out of beta.
Indeed - same here, and thanks for sharing!
Thank you!!!!
You're welcome!
Thanks for the great video Stephen. Is MicroOS now a level where you would use it in production? How does it stack up against Tumbleweed?
In my opinion as it's still in RC status I would keep it in testing - but the future is looking very promising!
@@stephenstechtalks5377 thank you! Hope you will keep following the project.
Fantastic lesson. One question: how is RAM allocated between the MicroOS host and a new container ? Is it possible to control that from the command line ?
Very interesting question! Containers are associated with tiny RAM overhead amounts compared to VMs. Distrobox front-ends Podman, and here's a blog post regarding memory:
www.decodednode.com/2022/12/container-memory-usage.html
More specifics regarding control from the command line:
github.com/89luca89/distrobox/blob/main/docs/useful_tips.md#apply-resource-limitation-on-the-fly
Cheers!
Indeed. Thanks and good luck!
You said Lazy...im Here...
:D
Hmm, I have been thinking about it for months. Immutable distros seem so pointless.
I was thinking "oh, nice, so my OS is like a blind, immutable host and I run everything in containers, so I won't end up with tons of orphaned packages and dependencies on the host when I install dev tools, remove things, etc".
Then I realized: Every user has to install copies of every app, which wastes disk space. All configuration must be repeated per-user instead of system-wide, which wastes time. And all package bloat is inside containers instead, so you still end up with huge lists of orphaned dependencies, but now they are inside a container that you must manually manage, so now you just have an extra layer of hard work to manage.
Oh and hey, you can use distro box on any distro if you really want to. I can't convince myself that immutable is a good idea, except for newbies who really only need Flatpaks. For developers, it's either a nightmare or totally pointless, since you can already run distrobox on any distro.
Nice walkthrough though!
Very interesting, thanks for sharing!
@@stephenstechtalks5377 Thank you again for the great video. I keep trying to convince myself of the benefits. :) There's a lot of drawbacks. But I can see one benefit, at least for Fedora Silverblue: They let you switch the immutable core to another one on the fly. So you can use the latest version of some desktop environment and then switch back if it wasn't stable. Or you could switch between KDE and GNOME on a daily basis.
Then again, I'm happy with my DE so I probably shouldn't start experimenting with others, because that way leads to an endless pit of re-configuring the desktop and learning new workflows. Doesn't it? ;) Hehe.
That reminds me, I need to subscribe to your channel!
Indeed, thanks for your support! :)
How can I edit some /etc config files?
Config files in /etc are completely editable in the normal way. :)
Show Master
Super!
Garuda pissed me off they hard lock most features of plasma work around! Open terminal sudo pacman -S plasma 😂 removes all of their crap Linux is about options what tf I want not what fits someone else! I have a special use because I have a ZenBook it has two screens plus I use a HDMI to a smart TV seeing I can watch movies ect on a 4k seeing my video card is 4k stremio is Great 👍
Zenbooks are cool, thanks for sharing!