• notfromhere@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    13 hours ago

    A lot of times it is necessary to build the container oneself, e.g., to fix a bug, satisfy a security requirement, or because the container as-built just isn’t compatible with the environment. So in that case would you contract an expert to rebuild it, host it on a VM, look for a different solution, or something else?

    • FlexibleToast@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      42 minutes ago

      Containerfiles are super easy to write. For the most part if you can do it in a VM, you can do it in a container. This sort of thing is why you would move to containers. Instead of being the “expert” in all the apps you run, you can focus on the things that actually need your attention.

    • WhyJiffie@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 hours ago

      It’s not like it’s so hard to rebuild a container for the occasional services that needs it. but it’s still much better than needing to do it with every single service

      • notfromhere@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 hours ago

        It depends on the container I suppose. There are some that are very difficult to rebuild depending on what’s in it and what it does. Some very complex software can be ran in containers.

        • FlexibleToast@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          40 minutes ago

          Yep, some people sort of miss the point of microservices and make some fairly monolithic containers. Or they’re legacy apps being shoehorned into a container. Some things still require handholding. FreeIPA is a good example. They have a container version, but it’s just a monolithic install in a container and only recommended for testing.