Was recently somewhat surprised that you can’t just copy a Rust executable into a ´scratch´ container and have it work, so this is a cool blog post to find in my RSS feed.

I’m guessing, if you’re doing something less complex, then you just need the ´musl´ target and the allocator…

    • Hexorg@beehaw.org
      link
      fedilink
      arrow-up
      1
      ·
      15 days ago

      That’s what I’m saying though - with statically linked binaries it’s just as easy to deploy the binary as it is the docker image.

      • Ephera@lemmy.mlOP
        link
        fedilink
        arrow-up
        5
        ·
        15 days ago

        You’re looking at it from the perspective of having coded a single application and wanting to deploy it. Try to think more like a sysadmin:

        • You’ve got a whole bunch of applications to deploy. Some of them may use dynamic linking, too.
        • You don’t know any of them too intimately, so want to just prevent them from interfering with each other, unless you allow it.
        • You want a uniform tool to manage all these different applications, and especially also when they’re allowed to interact.

        The result is deployment orchestration tools like Kubernetes, Docker Compose, Podman Compose etc… And as a dev, you have to provide a container image, if you want to play along in those.

        • Hexorg@beehaw.org
          link
          fedilink
          arrow-up
          1
          ·
          15 days ago

          Hmm there are plenty of tools to do that without containers… though I do see your point that docker provides a unified way of doing that which is easier.