

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.
Thanks for explaining it to me in a simple manner, I will update the url accordingly!