Oh no. This is so bad. Who in their right mind would assume that a login user remains the same user throughout the session!?

Oh wait. Windows.

? I’m agreeing with you?

There’s a difference between helping people with misunderstanding a tool and belittling them for being wrong. It’s just a matter of wording that separate an helpful answer from a toxic one

I could tell you “You should actually use Y instead of X. They are numerous benefits like A, B and C. The doc actually have a great example you may have missed or not understood it was for this purpose. It will help you a lot more than what you are thinking of doing.” And this would be fine.

But “Just use Y. X is bad because Y is made for that. You not willing to use Y shouldn’t make you do X. There’s even a the first Google link on how to do it” isn’t fine.

And I have not belittled them at all. I have said that it wasn’t what I was looking for. A lot of times people post questions they think should solve their issue, but only to realise that they didn’t fully understand the full picture and theirs problem is on a larger scale.

Seems like the best solution. I’ll look into it

But can it prevent killing only docker, and not the build/big containers processes?

Oh that’s not a problem to let a container get killed. It’s perfectly fine. What I want is just not crippling my whole server because one container did a funny.

If it keeps docker and the portainer VM I’ll be 100% ok, because I can just restart it. I don’t want to have remote access to my server outside of my home for security reasons, so this is just the bare minimum

Alright, sorry for calling it a “bandaid fix”. It wasn’t just the right term for what I wanted to say. I was more referring on how it would only fix issues in cases of builds, and not on actual runtime, which can also be an issue if I am not careful. So yeah, it’s the fix for the issue in the post, but this solution made me realise that this isn’t the only thing I want.

But the second part is… Just chill. It’s a home server. Not a high availability cluster. I can afford stupid things. Heck, I’m only asking this question because I got stupid and haven’t limited the job count of a cargo build, downing my server. I don’t care that my build crash. I just want to not have to manually restart it, because when I’m not here I can’t do it.

As for the link that you sent, it’s container limitations, not image building limitations. And I already have setup some on my most hungry container, stats shown that it blew past it, so idk what’s going on there.

Edit: NVM. This is a bandaid fix. What if you forgot to put the flag? Like it’s been 5 month since last time and forgot to do the same fix? Or you accidentally removed it while editing the command? I’m actually looking for a solution that fixed my problem fully, not a partial solution

Fair enough. But I don’t want a bandaid fix solution. Even more that I do all my docker through portainer and the option isn’t there.

It could also be useful if a container got a memory leak and is unbounded

I’ll try that. I know that systemctl has a start-or-reload command, but is there any “start-or-ignore” commands? Or start flags?

Let’s just hope that they won’t use it as a justification to put ads in your browser, or go the brave route.

Well it ses that bing is down too, and most independent search engines are a warper arround bing so…

I don’t know what’s the brand neW meta pick, but at least BTRFS over Ext4. BTRFS is just more stable and less corruptable than Ext4. Heck, fedora changed to it as default

I rather stay on java linux

There’s Listenbrainz, but it’s more artist based.

I got away with the original UI, but might check out this one too

After a day of using it, I can say that does the job. Thanks!

Yup. There is limitations still as some URLs are blocked like syncthing servers, but we’re free to add what we want

If you’re willing to use snaps, the next cloud snap is pretty great and easy to set up.

I’m not a fan of snaps nor how canonical push them, but this one gets a pass

Either flatpak or NixOs for me.

Flatpak is just light and doesn’t flood the user with 720710 lines just to say “installing Firefox”

NixOs just straight up has nothing to show.

Not sure if it’s clock related. I had a Debian 12 on a server that had a empty CMOS battery, and it didn’t do anything like that