• 0 Posts
  • 7 Comments
Joined 3 years ago
cake
Cake day: June 15th, 2023

help-circle

  • I’d say it’s because:

    1. the people who ask for recommendations won’t like (or understand) debian? (it’s just “old packages this” and “outdated that” for most people)
    2. the people who do use and appreciate debian don’t read “I hate windows pls recommend me a distro” posts (or at least don’t reply as often as the <insert popular distro> fanboys)

    And, no, I don’t use debian myself.

    but when I finally switched over to Debian, everything just worked!

    That’s most probably because you learned how to use your system without breaking it in the meantime :)




  • Should I just learn how to use Docker?

    Since you are not tied to docker yet, I’d recommend going with podman instead.

    They are practically the same and most (all?) docker commands work on podman too, but podman is more modern (second generation advantage) and has a better reputation.

    As for passing a network interface to a container, it’s doable and IIRC it boils down to changing the namespace on the interface.

    Unless you have specific reasons to do that, I’d say it’s much easier to just forward ports from the host to containers the “normal” way.

    There’s no limit to how many different IPs you can assign to a host (you don’t need a separate interface for each one) and you can use a given port on different IPs for different things .

    For example, I run soft-serve (a git server) as a container. The host has one “management” IP (92.168.10.243) where openssh listens on port 22 and another IP (192.168.10.98) whose port 22 is forwarded to the soft-serve container via podman run [...] -p 192.168.10.98:22:22).