Cette page est affichée en anglais. Une traduction française est en cours.
SkillsApr 16, 2026·3 min de lecture

Slim — Optimize Docker Containers with Automatic Minification

Slim (formerly DockerSlim) automatically analyzes and optimizes container images, shrinking them up to 30x by removing unnecessary files, packages, and layers.

AI Open Source
AI Open Source · Community
Prêt pour agents

Installation avec revue préalable

Cet actif nécessite une revue. Le prompt copié demande un dry-run, affiche les écritures, puis continue seulement après confirmation.

Needs Confirmation · 64/100Policy : confirmer
Surface agent
Tout agent MCP/CLI
Type
Skill
Installation
Single
Confiance
Confiance : Established
Point d'entrée
Slim Container Optimizer
Commande avec revue préalable
npx -y tokrepo@latest install bebccaab-3986-11f1-9bc6-00163e2b0d79 --target codex

Dry-run d'abord, confirmez les écritures, puis lancez cette commande.

TL;DR
Slim shrinks Docker images up to 30x by automatically removing unnecessary files and packages.
§01

What it is

Slim (formerly DockerSlim) automatically analyzes and optimizes Docker container images. It instruments your container, observes which files and libraries are actually used at runtime, then builds a minified image containing only those files. The result is an image that is up to 30x smaller with a reduced attack surface.

The tool targets DevOps engineers, security teams, and developers who want smaller, faster, and more secure container images without manually writing multi-stage Dockerfiles.

§02

How it saves time or tokens

Manually optimizing Docker images requires identifying unused packages, writing multi-stage builds, and testing that nothing breaks. Slim automates this entire process: run one command and get an optimized image. No Dockerfile changes needed. The smaller images also reduce registry storage costs and container pull times.

§03

How to use

  1. Install Slim: brew install slim or download from GitHub releases.
  2. Run Slim against your image: slim build my-app:latest.
  3. Use the optimized image: my-app.slim:latest.
§04

Example

# Install Slim
brew install slim

# Optimize a Node.js application image
slim build node-api:latest

# Compare sizes
docker images | grep node-api
# node-api        latest   890MB
# node-api.slim   latest    35MB

# Run the optimized image
docker run -p 3000:3000 node-api.slim:latest

# Advanced: keep specific paths and expose HTTP probes
slim build my-app:latest \
  --include-path /app/config \
  --http-probe-cmd /health
§05

Related on TokRepo

§06

Common pitfalls

  • Slim removes files not accessed during its probe phase. If your app has code paths not triggered during probing (e.g., error handlers, cron jobs), those files may be removed. Use --include-path to keep them.
  • The probe phase runs your container. Ensure the container can start and respond to health checks in the Slim environment.
  • Slim works best with server applications that have clear startup and request handling. Batch jobs or CLI tools may need custom probe commands.

Questions fréquentes

How does Slim know which files to keep?+

Slim instruments the container with syscall tracing during a probe phase. It runs the container, sends HTTP probes, and records every file accessed. Files not accessed are excluded from the optimized image.

Does Slim change my Dockerfile?+

No. Slim operates on built images, not Dockerfiles. It takes your existing image as input and produces an optimized copy. Your Dockerfile and build process remain unchanged.

How much can Slim reduce image size?+

Typical reductions are 5-30x depending on the base image and application. A 900MB Node.js image might shrink to 30-50MB. Alpine-based images see smaller reductions since they are already minimal.

Is the optimized image safe for production?+

Yes, with proper testing. Run your test suite against the optimized image before deploying. The main risk is missing files for code paths not exercised during the probe phase.

Does Slim support multi-platform images?+

Slim works on Linux amd64 and arm64 images. It does not currently support Windows containers. Multi-platform manifest support depends on the version.

Sources citées (3)
En lien sur TokRepo
DevOps ToolsMCP DockerFeatured workflows

Fil de discussion

Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.

Actifs similaires

Dive — Explore Docker Image Layers and Optimize Size

Dive is a tool for exploring Docker image contents layer by layer. It shows exactly what changed in each layer, identifies wasted space, and helps you optimize your Dockerfiles for smaller, more efficient container images.

Skills
AI Open Source

Docker Agent — Run Agent Tasks in Containers

Docker Agent packages agent workloads into containers so you get reproducible environments, clear boundaries, and safer runs than ad-hoc local scripts.

Skills
AI Open Source

Arcane — Modern Self-Hosted Docker Management Platform

A sleek, modern Docker management UI for creating, monitoring, and managing containers, images, volumes, and networks with a clean web dashboard.

Skills
Script Depot

Docker (Moby) — The Container Platform That Changed DevOps

Docker is the platform that popularized containerization. It packages applications with their dependencies into standardized containers that run consistently everywhere. Moby is the open-source project behind Docker Engine, the runtime that powers container-based development and deployment.

Skills
Script Depot
◈Accueil🔍Rechercher👤Moi