>>>>> Steinar Bang <[email protected]>: > What I would like to do, is to start with the official karaf image on > docker hub https://hub.docker.com/r/apache/karaf and then add a feature > as a part of the build process.
> Unless I've misunderstood, the images will be a lot smaller, because > they will only hold the difference between the base image and the > current state of the image file system at the end of the build. Hm... I've looked at the file system state of a priestine karaf 4.2.8 docker image, and maybe this wasn't such a good idea after all? https://hub.docker.com/layers/apache/karaf/4.2.8/images/sha256-90ab8758ddddf4f0b28afe7ca24b67456a9a8619be4cf5fc2fa90e3b26e64adf?context=explore A priestine karaf 4.2.8 image as an almost empty data directory, and the first thing that happens when karaf is started, is that e.g. data/cache/ is filled up with the running bundles, so the file system delta will be pretty big anyway. I.e. there will not be much space saved by this approach.
