Explore >> Select a destination
|
You are here 
|
www.augmentedmind.de | ||
| | | | |
enix.io
|
|
| | | | | This serie of articles deals with solutions for Docker image size optimization. In this first part, we talk about *multi-stage build*. We also explain differences between static and dynamic libraries and why it matters. We also describe the use of the famous Alpine Linux distribution. | |
| | | | |
www.ardanlabs.com
|
|
| | | | | Series Index Reducing Image Size Details Specific To Different Languages Going Farther To Reduce Image Size Introduction In the first part, we introduced multi-stage builds, static and dynamic linking, and briefly mentioned Alpine. In this second part, we are going to dive into some details specific to Go. Then we will talk more about Alpine, because it's worth it; and finally we will see how things play out with other languages like Java, Node, Python, Ruby, and Rust. | |
| | | | |
some-natalie.dev
|
|
| | | | | Some containers are big, but reliably reducing their size isn't difficult or complicated. Let's start simple by tidying our container's build steps. | |
| | | | |
www.foonathan.net
|
|
| | | Let me share a useful insight with you: constexpr is a platform. Just like you write code that targets Windows or a microcontroller, you write code that targets compile-time execution. In both cases you restrict yourself to the subset of C++ that works on your target platform, use conditional compilation if your code needs to be portable, and execute it on the desired target platform. You can thus view constexpr as another platform you can target; it just so happens to be run by your compiler. This insig... | ||
