Why statically compiling and using SCRATCH are important (Kill The Cruft!)
summary
Shows converting an ANSI C listener into a container using a statically linked binary and the scratch keyword in a Dockerfile, replacing a 193 MB dynamic-image build with a 1.1 MB static-image build (dynamic binary ~20 KB, static binary ~1.1 MB). Demonstrates that static linking puts libraries inside the binary, eliminates an OS layer so no docker exec shell, and yields much smaller images, faster pushes and reduced attack surface.
AI-written summary · about
related talks
14mSmall Containers? or Small Images?
49mScratch containers and the supply chain trouble
36mBuild a Container Image from Scratch
27mDocker Image Journey - How to Shrink a Docker Image
34mDefence Against the Docker Arts
01h 00mDocker, FROM scratch
59mBeyond Docker Buzzwords
30mLearning by Pulling Things Apart