![]() Looking at our monster CI container image One of these is called distroless by Google. for Go and Java, without adding any operating system specific files. If you do not want to go that far, there are base images specific to the application runtime you are using, e.g. it does not even add a layer to your image. Which has not only 0 MB (or in words ZERO MEGABYTES) but is also a no-op (a no-operation), i.e. However, if you want to make your base image even smaller, you might need to invest some time in making it compatible with another distribution or even with another libc implementation.įor the very adventurous, one can also use scratch as a base image. ![]() More about that later when we fully minimize our image layers. Which saves a lot of space, because tracking file changes for updates, increases your image size dramatically. Surely the Ubuntu team is looking into that already.)Īnother aspect of keeping your base image up-to-date is that you do not need to update as part of your image definition. (Why the latest versions are a few MB bigger than 18.04 is left as an exercise for the reader. ![]() Here is a list of the latest images:Īs you can see, an upgrade is not only worth the time because of better software but also because of the smaller image sizes. However, the ubuntu image changed over time and it is worth upgrading. The most used base image, ubuntu, is already very optimized. Choosing a smaller base image is therefore the first and probably the easiest way of reducing the size of your images. However, this generalization comes at the cost of including more libraries and tools that your application might not need. Base images allow to very quickly apply security and bugfix updates to your whole container based software infrastructure since a good base image serves as a general common installation. Use a smaller base image or libcĮvery container image is based upon a so called base image ( see the FROM instruction) that allows you to reuse configurations, packages and other files across different images. Splitting up processes and services for breaking up imagesĪs with everything in the world of software development and infrastructure, we can rely on best practices that others have already established by most likely wading through hours of painful research.Fully minimize and tidy up image layers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |