I am looking for something that can take a Dockerfile, like the following as an input:


FROM --platform=linux/amd64 debian:latest
ENV DEBIAN_FRONTEND=noninteractive

RUN apt update && apt install -y curl unzip libsecret-1-0 jq
COPY entrypoint.sh .
ENTRYPOINT [ "/entrypoint.sh" ]

And produce a a multi-stage Dockerfile where the last stage is built from scratch, with the dependencies for the script in the ENTRYPOINT (or CMD) copied over, like this:


FROM --platform=linux/amd64 debian:latest as builder
ENV DEBIAN_FRONTEND=noninteractive

RUN apt update && apt install -y curl unzip libsecret-1-0 jq

FROM --platform=linux/amd64 scratch as app
SHELL ["/bin/bash"]

# the binaries executed in entrypoint.sh
COPY --from=builder /bin/bash /bin/bash
COPY --from=builder /usr/bin/curl /usr/bin/curl
COPY --from=builder /usr/bin/jq /usr/bin/jq
COPY --from=builder /usr/bin/sleep /usr/bin/sleep

# shared libraries of the binaries
COPY --from=builder /lib/x86_64-linux-gnu/libjq.so.1 /lib/x86_64-linux-gnu/libjq.so.1
COPY --from=builder /lib/x86_64-linux-gnu/libcurl.so.4 /lib/x86_64-linux-gnu/libcurl.so.4
COPY --from=builder /lib/x86_64-linux-gnu/libz.so.1 /lib/x86_64-linux-gnu/libz.so.1
# ...a bunch of other shared libs...

# entrypoint
COPY entrypoint.sh /entrypoint.sh

ENTRYPOINT [ "/entrypoint.sh" ]

I’ve had pretty decent success creating images like this manually (using ldd to find the dependencies) based on this blog. To my knowledge, there’s nothing out there that automates producing an image built from scratch, specifically. If something like this doesn’t exist, I’m willing to build it myself.

    • trevor@lemmy.blahaj.zoneOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 months ago

      Oh wow. I didn’t realize that Nix containers built from scratch. That’s exactly what I wanted (minus having to learn Nix, but that’s not too bad, honestly).

      • trevor@lemmy.blahaj.zoneOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        9 months ago

        Never mind. While Nix containers do get you the small image sizes and predictable builds you want, nix, the package manager, is basically broken on macOS.

        I use Linux, where nix seems to work totally fine, but the other people I’m working with use macOS, so I can’t ask them to install something that won’t work to produce images correctly.

        I think I’m going to have to build the minimizer I was thinking of.

  • friend_of_satan@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    10 months ago

    I feel like at this point you should just build statically linked binaries, but I suppose there are cases where that’s not going to be possible. Anyhow, I’ve never seen anything like that.

    • trevor@lemmy.blahaj.zoneOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 months ago

      Yeah. Statically-linked binaries are awesome, but many of the utilities that I need to run would require lots of changes to the source to make it happen.

  • Kangie@lemmy.srcfiles.zip
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    9 months ago

    We have Kubler which makes Gentoo -based images. It does a great job of enabling you to toggle dependencies that you need and building a slim, hardened image.

    Edit: lddsucks, try libtree instead.