I’m a retired Unix admin. It was my job from the early '90s until the mid '10s. I’ve kept somewhat current ever since by running various machines at home. So far I’ve managed to avoid using Docker at home even though I have a decent understanding of how it works - I stopped being a sysadmin in the mid '10s, I still worked for a technology company and did plenty of “interesting” reading and training.

It seems that more and more stuff that I want to run at home is being delivered as Docker-first and I have to really go out of my way to find a non-Docker install.

I’m thinking it’s no longer a fad and I should invest some time getting comfortable with it?

  • Great Blue Heron@lemmy.caOPEnglish
    26·
    11 months ago

    Well, that wasn’t a huge investment :-) I’m in…

    I understand I’ve got LOTS to learn. I think I’ll start by installing something new that I’m looking at with docker and get comfortable with something my users (family…) are not yet relying on.

    • infeeeee@lemm.eeEnglish
      26·
      11 months ago

      Forget docker run, docker compose up -d is the command you need on a server. Get familiar with a UI, it makes your life much easier at the beginning: portainer or yacht in the browser, lazy-docker in the terminal.

      • ChapulinColorado@lemmy.worldEnglish
        22·
        11 months ago

        I would suggest docker compose before a UI to someone that likes to work via the command line.

        Many popular docker repositories also automatically give docker run equivalents in compose format, so the learning curve is not as steep vs what it was before for learning docker or docker compose commands.

      • damnthefilibuster@lemmy.worldEnglish
        71·
        11 months ago

        Second this. Portainer + docker compose is so good that now I go out of my way to composerize everything so I don’t have to run docker containers from the cli.

        • infeeeee@lemm.eeEnglish
          4·
          11 months ago

          like just docker run by itself, it’s not the full command, you need a compose file: https://docs.docker.com/engine/reference/commandline/compose/

          Basically it’s the same as docker run, but all the configuration is read from a file, not from stdin, more easily reproducible, you just have to store those files. The important is compose commands are very important for selfhosting, when your containers expected to run all the time.

          RTFM: https://docs.docker.com/compose/

          • Great Blue Heron@lemmy.caOPEnglish
            5·
            11 months ago

            Yeah, I get it now. Just the way I read it the first time it sounded like you were saying that was a complete command and it was going to do something “magic” for me :-)