cestvrai

You need a reverse proxy to accomplish this. The reverse proxy will have port 80 exposed and points PiHole/Searx containers and their respective ports for the paths you specify.

Sounds like end-to-end encryption is opt-in. Thus, a default configuration leaves communications unencrypted and vulnerable to eavesdropping.

I have a Pi4 running octoprint, pi-hole and some of my own containers.

The rest I run on a Hetzner VM.

Google is terrible and could have updated sooner, but not their responsibility.

I don’t see why residents did not construct a makeshift barricade themselves after years of inaction.

I have worked with Docker/WSL for a number of years and it is more difficult compared to Docker in Linux. There are a lot a unique quirks and bugs that are an absolute pain to deal with.

Would not recommend for any relatively complex use case and certainly not for a server.