Skip to main content
Account

Slim Toolkit

Slim Toolkit minimizes container images by keeping only the files a workload uses. Learn how slim build, xray and lint cut size and attack surface.

Status
Stable
Category
Provisioning
Subcategory
Security & Compliance
License
Apache-2.0
Technology matrix Graveyard Tried, got burned, walked away See the matrix

Slim Toolkit (formerly DockerSlim) analyzes container images and produces minimized versions that contain only the files a workload actually uses at runtime. Typical results are 10x to 30x smaller images with a drastically reduced attack surface, without requiring the application to be rewritten for a distroless or scratch base.

The core slim build command runs the source image, probes the application using HTTP/TCP probes, unit tests, or a user-supplied script, and traces system calls and file access to learn which binaries, libraries, and config files are actually touched. It then generates a new image containing only those artifacts, optionally re-applying seccomp and AppArmor profiles derived from the observed syscalls. Other commands include xray for static analysis of image layers and lint for Dockerfile inspection.

Slim Toolkit is used as a post-build hardening step in CI pipelines where teams want to ship smaller, more secure images from familiar base images like node, python, or openjdk without maintaining custom minimal base images themselves.

Slim Toolkit recordings

2 recordings, newest first

Security & Compliance

Email signup loads here. You can also manage email preferences in account settings.

Build Slim Toolkit? I'll show you where engineers get stuck with it โ†’ Back free content for the community โ†’