Comment on Podman: Issues with multiple users running containers simultaneously

• rhymepurple@lemmy.ml ⁨6⁩ ⁨days⁩ ago

  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?

  original
• Overspark@piefed.social ⁨1⁩ ⁨week⁩ 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.

  original

  • rhymepurple@lemmy.ml ⁨6⁩ ⁨days⁩ ago

    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.

    original

    • Overspark@piefed.social ⁨6⁩ ⁨days⁩ ago

      You can use the per-user reverse proxies as a bridge between the host network and the user-specific internal network. So for a user coming from outside the path looks like this:

      User -> main reverse proxy on main IP and port 80/443 -> user-specific proxy listening on main IP with port 8080 and proxying to user-specific internal network -> destination container listening on user-specific internal network.

      And for a container running as a different user the path will be the same, but the user-specific reverse proxy will be listening on port 8081 and higher for example.

      original

      • rhymepurple@lemmy.ml ⁨6⁩ ⁨days⁩ ago

        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?

        original

        • -> View More Comments