Explore >> Select a destination
|
You are here 
|
wimpysworld.com | ||
| | | | |
www.trevorlasn.com
|
|
| | | | | Streamline your development and deployment processes | |
| | | | |
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. | |
| | | | |
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. | |
| | | | |
blog.oddbit.com
|
|
| | | Someone asked on IRC about running ntpd in a container on Atomic, so I've put together a small example. We'll start with a very simple Dockerfile: FROM alpine RUN apk update RUN apk add openntpd ENTRYPOINT ["ntpd"] I'm using the alpine image as my starting point because it's very small, which makes this whole process go a little faster. I'm installing the openntpd package, which provides the ntpd binary. By setting an ENTRYPOINT here, the ntpd binary will be started by default, and any arguments passed t... | ||
