OK now this would make some sense but would definitely be a bit of a show stopper for me. I’ll give it a try though.
Comment on Podman: Issues with multiple users running containers simultaneously
rhymepurple@lemmy.ml 9 hours ago
This is due to a security design deicison of Podman. Each user’s network(s) is only available to that user. This is great for most services, but can cause issues for some services - especially reverse proxies. Unfortunately, I’m not aware of an ideal solution. The only solution I’ve seen is moving the reverse proxy to another host and exposing the services’ ports on the localhost. I hope someone can provide a better solution!
MoogleMaestro@lemmy.zip 8 hours ago
Overspark@piefed.social 8 hours ago
The solution to this can be multiple reverse proxies. Each user runs it’s own reverse proxy (if you actually need one, otherwise you let the container bind directly to a port on the host system). Then you run one main reverse proxy on port 80/443 that proxies to those other ports based on hostname.
The upside of this construction is that containers running as different users can’t directly access each others internal networks, which is much better for security, as those networks often contain barely protected services, which is why you’re using a reverse proxy in the first place.
robber@lemmy.ml 8 hours ago
No expert but don’t the logs look like the requests are coming through?