No kidding. This solves a major issue with the Steam Deck as well, because now someone else can be playing on the Deck while you use your main PC for another game.
You should do it. Easy to setup using either their official AIO image or the community-driven micro service one. I am using the latter and it's been amazing. It's completely replaced Google Drive, Calendar, and Contacts for me and with the DAVx5 Android App it feels like a drop-in replacement. I am also using the auto upload feature to back up my photos to it.
I use podman with the podman-docker compatibility layer and native docker-compose. Podman + podman-docker is a drop-in replacement for actual docker. You can run all the regular docker commands and it will work. If you run it as rootful, it behaves in exactly the same way. Docker-compose will work right on top of it.
I prefer this over native Docker because I get the best of both worlds. All the tutorials and guides for Docker work just fine, but at the same time I can explore Podman's rootless containers. Plus I enjoy it's integration with Cockpit.
Settings and internet are fine. I dunno what to tell you. Very frequently Windows update shows its head, like I'll randomly want to restart my computer because I installed a piece of software that required it, and then it kicks off a long round updates when I just want to use my computer.
I still think having to leave it on and let it run in the background is still just addressing the symptoms. An update process should be way faster than that so that such a thing isn't needed.
I turn off modern standby. I don't want my computer turning on when I am not around or when I am asleep. For laptops, modern standby is famous for turning it on while its in your laptop bag, causing overheating and battery drainage.
I think if an update process is annoying enough to require something like Modern Standby in order to be "seamless", it needs to be improved.
Cockpit definitely has the ability to create bridge devices. I haven't found a tutorial specifically for cockpit, but you can follow something like this and apply the same principles to the "Add Bridge" dialog in Cockpit's network settings.
Wtf is this crap? How is it MY problem when other OSes do a much better job with the update process? You talk about 15 minutes or leaving updates running overnight as if that's decent. I can do a Linux update within 2 minutes and get my system back up by minute 3. That's the kind of performance I am expecting and I don't even need a super fast NVMe drive to do it.
The fact that you're okay with putting up with Window's comparatively slow update speed and then have to make excuses for it by saying that the USER needs to constantly baby it or waste power by leaving it overnight is honestly hilarious. To be quite frank, you just don't know how updates could be better because you're just used to what Windows has always offered you.
Don't put the blame on users for a problem that Microsoft can definitely solve but never does.
Most updates on my system are handled overnight, outside the active hours I’ve set in the settings.
Not everyone leaves their computer on draining power. I always put it to sleep when I am not using it. If your argument is that, yeah updates aren't a problem, you just let your computer run and chew on it for a long time, that's still a problem...
I am guessing you run your computer all the time instead of putting it to sleep, because it's never a process that completes transparently in the background for me. It will always build up and then I have to go in and manually trigger it. Or I have to restart because I installed a new application that requires it and then it decides to do them all at once and takes forever.
The longest update I’ve had took about 15 minutes.
Asking someone to take 15 minutes out of their work time to do updates is exactly why people DON'T want to update. Even 15 minutes is insane. That's a whole standup meeting, that's a whole presentation, that's work disruption for a bunch of people.
Linux updates in a minute. That's the kind of performance we SHOULD be expecting in the modern age and that Microsoft refuses to deliver.
Problem with this is that it's really hard to figure out whether some update to some minor library is going to affect an application. Sometimes you don't even know which applications are using that library.
Your containers show up in Cockpit under the "Podman containers" section and you can view logs, type commands into their consoles, etc. You can even start up containers, manage images, etc.
Are there any tutorials on how to do this from Cockpit?
I have not done this personally, but I would assume you need to create a bridge device in Network Manager or via Cockpit and then tell your VM to use that. Keep in mind, bridge devices only work over Ethernet.
There is occasional weirdness if you don't powercycle though. In particular, certain KDE updates will make the desktop misbehave until you reboot. I get where you're coming from though. Quick updates and the ability to decide when you want to restart means that I have no qualms about updating frequently.
I am on Arch too and pacman -Syu is usually a snack I have with my morning tea.
Yeah, I pay for Netflix, Hulu, and Amazon Prime and yet, I am still downloading shows that are on those services because their shitty DRM schemes limit me to 720p. It's insanity.
I am using it as a migration tool tbh. I am trying to get to rootless, but some of the stuff I host just don't work well in rootless yet, so I use rootful for those containers. Meanwhile, I am using rootless for dev purposes or when testing out new services that I am unsure about.
Podman also has good integration into Cockpit, which is nice for monitoring purposes.
I mean, I don't think I would mind forced updates if they didn't take so damned long and fail half the time. And then, just when you think you've finished installing all updates, you reboot and there's more updates! Why can't they just install it all at once?
Plus, after each major update, Microsoft wastes your time by advertising to you about Edge, Office 365, and OneDrive before they even let you get back into the desktop.
Forced security updates is addressing a symptom but not addressing the root cause, which is that the Windows update process is just painful for a myriad of reasons. In Linux, I run one command, wait 5 minutes, reboot, and I am back to work.
It isn't that much better. I use it as drop-in docker replacement. It's better integrated with things like cockpit though and the idea is that it's easier to eventually migrate to rootless if you're already in the podman ecosystem.
podman-compose is different from docker-compose. It runs your containers in rootless mode. This may break certain containers if configured incorrectly. This is why I suggested podman-docker, which allows podman to emulate docker, and the native docker-compose tool. Then you use sudo docker-compose to run your compose files in rootful mode.
No kidding. This solves a major issue with the Steam Deck as well, because now someone else can be playing on the Deck while you use your main PC for another game.