Kellnr's docker image doubled in size in last release about kellnr HOT 4 CLOSED

#255 (comment)

I understand that the doc build is executed inside the kellnr docker container, so these dependencies are only needed to build docs hosted on kellnr?

This will only become more and more.

docs.rs and crater are using our own crates-build-env container, see also https://docs.rs/about/builds, and the list of installed packages is long.

from kellnr.

Thanks for reporting. I see a general conflict of interest in what Kellnr wants to achieve.

1. It should be very easy to setup and use. Just one docker run -> That speaks for a build-in doc.rs build
2. It should be small enough to run on low-end hardware -> This speaks for a separat builder

The only option which would solve both is to split Kellnr into three images.

1. The full image with a build in doc.rs builder (what we have now)
2. A minimal Kellnr image without the doc.rs build
3. A builder container which can be used as a sidecar for the 2. to build if needed

With this option, a user can decide if he needs the docs.rs build and if he wants one large image or two smaller one. Unfortunately that is a lot of work to implement.

from kellnr.

another factor I can imagine:

if kellnr is used more as a private registry, it's totally fine to just extend the main kellnr docker container with the system dependencies your packages need.

If you use kellnr more as a mirror of crates.io, you'll need the full image over time.

from kellnr.

two other things to add because I just had to look it up for another question:

• we also have a linux-micro container which just includes build-essential packages: https://github.com/rust-lang/crates-build-env/blob/master/linux-micro/packages.txt
• rustwide (the library that docs.rs & crater use to run the builds) has an example how a containerized doc-build could work: https://github.com/rust-lang/rustwide/blob/master/examples/docs-builder.rs

from kellnr.