• Vendetta9076@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    5 hours ago

    First of all: no, and repeating this nonsense over and over doesn’t make it any more true.

    Second of all: I truly will never understand the hatred some people have for docker. If you prefer all bare metal install, then fine. But constantly shouting from the rooftops how useless and bad docker is seems a little silly.

    • Solumbran@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      2 hours ago

      Containers are fine but docker is a pain in the ass that lazy people use when they don’t want to provide clean installation/packaging.

      How many times have I seen an equivalent of “we use a custom fork of an obsolete version of an unmaintained package, so if you want to compile it yourself good luck because we forgot how we even did it. Alternatively, you can install the docker version”…

  • SavvyWolf@pawb.social
    link
    fedilink
    English
    arrow-up
    0
    ·
    6 hours ago

    Honestly, since getting into NixOS, I’ve found that much more of an elegant system than Docker or whatever.

  • 𝘋𝘪𝘳𝘬@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    7 hours ago

    So they say I can run a dozen of different web applications on the same machine all on the same port internally and different port externally and have a reverse proxy forwarding the traffic to the correct port based on the hostname it was called with by simply using a bunch of chrooted environments?

    • IsoKiero@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 hours ago

      Not that it’s really relevant for the discussion, but yes. You can do that, with or without chroot.

      That’s obviously not the point, but we’re already comparing oranges and apples with chroot and containers.

  • nous@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 hours ago

    Um no. Containers are not just chroot. Chroot is a way to isolate or namespace the filesystem giving the process run inside access only to those files. Containers do this. But they also isolate the process id, network, and various other system resources.

    Additionally with runtimes like docker they bring in vastly better tooling around this. Making them much easier to work with. They are like chroot on steroids, not simply marketing fluff.

    • Markaos@lemmy.one
      link
      fedilink
      arrow-up
      0
      ·
      4 hours ago

      The author acknowledges that, the blog post seems to be aimed at demystifying the concept of namespaces by showing that a “container runtime” that only does limited filesystem namespaces (using chroot) is enough to get some widely used containers running (of course without all the nice features and possibilities of the other types of namespaces)