

Yeah, I think the rite of passage is the infamous:
sudo rm -rf /. --no-preserve-root


Yeah, I think the rite of passage is the infamous:
sudo rm -rf /. --no-preserve-root


Ah, that makes sense, thanks for clearing it up for me. It’s several containers but now that I know what I’m looking for, I’ll be able to figure it out. I was just living in blissful ignorance until now.


Thank you so much for your detailed answer. That brought me up to speed. I just never questioned it and, as you said, assumed that it was to test network connectivity.
It also finally explains the issues with those containers I kept having every few months. It always fixed itself before I had the time to actually look into it, but it has always been bugging me. This time I was able to actually catch it.
I’ll update the health checks to the proper URL im using, or should I use localhost:port?
Anyway, thanks again!


I honestly didn’t know this was the case. Still learning on this journey of self hosting. What exactly do I use for the health check then?


Yeah saw that and checked the time, both on the host and container. Both are accurate.
T14 Gen 2 with Ryzen here. Great machine, no problems at all.


This face almost made me downvote you.
I’ve tried boiling pasta in ocean water. They were inedible.


It would be absolutely hilarious, if the whole thing wasn’t so sad. Nevertheless, it’s a welcome change of direction in this war and shows what a determined country and army can do against such a big aggressor.
I just hope it actually changes something in the end. Let’s hope Putler meets his window to fall out of soon.
Thanks for explaining it to me in a simple manner, I will update the url accordingly!