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

  • Nibodhika@lemmy.worldEnglish
    0·
    9 months ago

    You’re not forced to use dockerhub or kubernetes, in fact I use neither. Also if a team chooses to host their images on dockerhub that’s their choice, it’s like saying git is bad because Microsoft owns GitHub, or that installing software X from the repos is better than compiling because you need to use GitHub to get the code.

    Also docker images can also be easily mirrored, archived offline etc, and they will keep working after the packages you archived stop because the base version of some library got updated.

    • TCB13@lemmy.worldEnglish
      0·
      9 months ago

      Yet people chose to use those proprietary solutions and platforms because its easier. This is just like chrome, there are other browser, yet people go for chrome.

      It’s significantly hard to archive and have funcional offline setups with Docker than it is with an APT repository. It’s like an hack not something it was designed for.

      • Nibodhika@lemmy.worldEnglish
        0·
        9 months ago

        It’s definitely much easier to do that on docker than with apt packages, and docker was designed for thst. Just do a save/load, https://docs.docker.com/reference/cli/docker/image/save/ and like I mentioned before this is much more stable than saving some .deb files which will break the moment one of the dependencies gets updated.

        Most people will use whatever docker compose file a project shows as default, if the project hosts the images on dockerhub that’s their choice. Plus I don’t understand what’s the problem, GitHub is also proprietary and no one cares that a project is hosted there.

        • TCB13@lemmy.worldEnglish
          0·
          9 months ago

          It’s definitely much easier to do that on docker than with apt packages,

          What a joke.

          Most people will use whatever docker compose file a project shows as default, if the project hosts the images on dockerhub that’s their choice

          Yes and they point the market in a direction that affects everyone.

          GitHub is also proprietary and no one cares that a project is hosted there.

          People care and that’s why there are public alternatives such as Codeberg and the base project Gitea.

          • Nibodhika@lemmy.worldEnglish
            1·
            9 months ago

            Got it, no one should use software hosted on GitHub, you’re either a teenager who just discovered Linux a couple of years ago or a FOSS fundamentalist, in any case I’ve had the personal policy of not to waste time with either for over 20 years.