You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would improve the size and the security of the images, because the build tools would stay in the builder step image. Then we only transfer the required compiled assets and have a final image that is minimal and that only contains the runtime and the executed code.
codeofmochi
changed the title
What do you think about using [multi-stage builds](https://docs.docker.com/build/building/multi-stage/) ? IMO this would be better, because the build tools would stay in the builder step image. Then we only transfer the required compiled assets and have a final image that is minimal and that only contains the runtime and the executed code.
Use multi-stage builds in Dockerfiles
Aug 4, 2023
Should we use multi-stage builds?
This would improve the size and the security of the images, because the build tools would stay in the builder step image. Then we only transfer the required compiled assets and have a final image that is minimal and that only contains the runtime and the executed code.
See original discussion in #33 (comment)_
Other links:
The text was updated successfully, but these errors were encountered: