Hi, I’ve been thinking for a few days whether I should learn Docker or Podman. I know that Podman is more FOSS and I like it more in theory, but maybe it’s better to start with docker, for which there is a lot more tutorials. On the other hand, maybe it’s better to straight up learn podman when I don’t know any of the two and not having to change habits later. What do you think? For context, I know how containers works in theory, I know some linux I think well, but I never actually used docker nor podman. In another words: If I want to eventually end up with Podman, is it easier to start with docker and then learn Podman, or start with Podman right away? Thanks in advance

  • Victor@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    9 months ago

    People love to hate on people who don’t care for containers.

    Maybe so. 😕

    what it means to run code on bare metal

    I’m guessing it means something slightly different than what most people think, namely to just run it in the OS. Would you explain to me what it really means?

    • SpaceNoodle@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 months ago

      Bare metal would mean without an OS to manage peripherals, resources, even other tasks - like you might find on a resource-constrained embedded system.

    • ImTryingLemmy@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      9 months ago

      The OS is in between the service and the bare metal. Something like OPNsense can be said to be running on bare metal because the OS and the firewall service are so intertwined. However, something like firewalld isn’t running on the bare metal because it’s just a service of the operating system.

      That’s how I understand it anyway, I’m not a pro