@rhymepurple@lemmy.ml
member since 29 Nov 2021 03:42
comments
- on Podman: Issues with multiple users running containers simultaneously in c/selfhosted@lemmy.world · 5 Sep 2026
-
on Podman: Issues with multiple users running containers simultaneously in c/selfhosted@lemmy.world · 5 Sep 2026
I think this is what OP was originally trying, but this approach breaks when each service’s Podman service runs on its own localhost user.
-
on Podman: Issues with multiple users running containers simultaneously in c/selfhosted@lemmy.world · 5 Sep 2026
I didn’t see the logs when I originally posted. However, I’m not sure what the logs indicate. It could be that nginx successfully received the request and received an authorization error from Podman’s networking stack then returned a 503 error to the client (or logged the 503 response that was returned to nginx).
-
on Podman: Issues with multiple users running containers simultaneously in c/selfhosted@lemmy.world · 5 Sep 2026
I’m not trying to convince you of this solution (I personally don’t like it), but I am curious what didn’t work for you. Were you unable to get the reverse proxy to serve each service? Were you unable to have the services behind the reverse proxy to talk to each other?
-
on Podman: Issues with multiple users running containers simultaneously in c/selfhosted@lemmy.world · 4 Sep 2026
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!
This would require the main proxy running as root or with some other sort of elevated privileges to allow cross-user network access though, right? If so, wouldn’t that essentially make the user-specific reverse proxy unnecessary in most cases?