Or maybe a two click solution? :)

  • soft_frog@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Docker is basically a virtual machine image you write your software in. Then when you run the software you don’t need to worry about compatibility or having the right dependencies installed, it’s all included in the docker image.

    Think of Docker as being Nintendo cartridges that you can take to any friends house, plug them in, and play. Servers can run more than one Docker container.

    The approach greatly simplifies writing code and having it work on your server, reduces errors, and adds a layer of security.

    • ElectroVagrant@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      I’ve read and reread, listened and relistened to info on docker/containers and I still feel like I’m missing something tbh.

      Let’s say you have a docker container for something and it’s for a Linux distro, that won’t run on another OS, will it? Maybe not even a different Linux distro from the one it was made for (e.g. Ubuntu or Arch or Fedora or whatever).

      To go off your example, Docker’s not like an expansion module to make your Switch games work on a PlayStation or Xbox…Right? There seems to be some kind of mixed messaging on this, the way they’re so readily recommended (which seems to be related to a presumption of familiarity that often isn’t there toward those inquiring).

      I guess I’ve also been confused because like…Shouldn’t old installers handle bundling or pulling relevant dependencies as they’re run? I’d imagine that’s where containers’ security benefits come into play though, alongside being virtualized processes if I’m not mistaken.