Use your own custom images for image size optimisation

[oliviermbida]

File: build/building/multi-stage.md
For multi-stage builds to be efficient you need to know what is inside your docker images including the official docker images.
The advantages of using multi-stage builds relies on docker's layering and if the images being layered themselves contain unused packages that advantage is wasted.
This point may be obvious to experts but no where is this emphasised.
There are also issues with these claims:

• "Multi-stage builds are useful to anyone who has struggled to optimize Dockerfiles while keeping them easy to read and maintain."

• "Multi-stage builds allow you to drastically reduce the size of your final image, without struggling to reduce the number of intermediate layers and files"

I wrote this to explain why these claims don't stand up to scrutiny

Docker's Best practices

In short , Multi-stage builds does not allow you to drastically reduce the size of your final image rather the sizes of the images you choose for your stages allows you that. Image size optimisation is reducing the size of the image itself not choosing another image.

[docker-robott]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked