Comment on How I reduced the size of my very first published docker image by 40% - A lesson in dockerizing shell scripts

MonkderZweite@feddit.ch ⁨1⁩ ⁨year⁩ ago

• otl@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

  The art of turning a 500-line text file into a 50MB tarball. Welcome to the future :(

  source
• dataprolet@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

  Yeah, wtf, why would you do that?

  source

  • domi@lemmy.secnd.me ⁨1⁩ ⁨year⁩ ago

    Environments like Kubernetes only run containers so you would deploy any shell script with containers as well.

    source

    • Carighan@lemmy.world ⁨1⁩ ⁨year⁩ ago

      But you’d use the shell script as part of something else, surely? As in, it’s not a container, it’s something deployed as part of or copied into a container?

      source

      • domi@lemmy.secnd.me ⁨1⁩ ⁨year⁩ ago

        That depends, we have quite a few images that are just a single shell script or a collection of shell scripts which run as jobs or cronjobs. Most of them are used for management tasks like cleaning up, moving stuff or debugging.

        Has the big advantage of being identical on each node so you don’t have to worry about keeping those shell scripts up to date with volumes. Very easy to just deploy a job with a debug image on every node to quickly check something in a cluster.

        Of course, if the shell script “belongs” to an application you might as well add the shell script in the application container and override the start arguments.

        source
  • ikidd@lemmy.world ⁨1⁩ ⁨year⁩ ago

    So you know what your dependencies are.

    source