菜单
Picking the right Docker base image for mise — debian:slim vs ubuntu vs alpine (with the musl caveat) vs nvidia/cuda vs mcr.microsoft.com/devcontainers/base. Covers glibc vs musl, tool compatibility, and image-size trade-offs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
End-to-end recipe for a modern C++ project managed by mise — cmake + ninja + ccache + mold linker + clang-tools + optional conan package manager. Full CMakePresets.json, mise.toml tasks, and first-run walkthrough. Use when starting a new C++ project or modernizing an existing one.
End-to-end recipe for a Docker-based dev loop with mise — multi-stage Dockerfile with mise pre-installed, docker-compose for services (Postgres, Redis), BuildKit cache mounts, and mise tasks that wrap compose. Use when running dev entirely in containers or prod-parity testing.
End-to-end recipe for a Go HTTP service managed by mise — Go + air (hot reload) + golangci-lint + gotestsum + a Dockerfile hint for production. Complete mise.toml template, first-run walkthrough, and common gotchas. Use when starting a new Go service or adding mise to an existing one.
End-to-end recipe for a Neovim configuration managed by mise — the vim.env.PATH prepend pattern, LSPs installed via mise (npm:pyright, aqua:gopls, etc.), conform.nvim for formatters, and the mise-managed "editor as a tool" approach. Use when setting up a modern Neovim config that plays nicely with mise-managed projects.
End-to-end recipe for a Next.js app managed by mise — Node + pnpm (via corepack) + TypeScript + Prettier + ESLint + Playwright. Complete mise.toml template, first-run walkthrough, and common gotchas. Use when starting a new Next.js app or adding mise to an existing one.
End-to-end recipe for a FastAPI service managed by mise — Python + uv + ruff + pytest + a Postgres env var. Complete mise.toml template, first-run walkthrough, and common gotchas. Use when starting a new FastAPI project or adding mise to an existing one.
基于 SOC 职业分类
| name | mise-docker-base-images |
| description | Picking the right Docker base image for mise — debian:slim vs ubuntu vs alpine (with the musl caveat) vs nvidia/cuda vs mcr.microsoft.com/devcontainers/base. Covers glibc vs musl, tool compatibility, and image-size trade-offs. |
mise itself runs fine on most bases, but the tools mise installs have opinions about glibc, system libraries, and architecture. Picking the wrong base is the #1 cause of "works on my machine but not in CI" bugs with containerized mise.
| Use case | Base image | Why |
|---|---|---|
| General dev / polyglot | debian:12-slim | glibc, small, broad compatibility with mise-managed tools |
| Ubuntu shop | ubuntu:24.04 | Same story, just the team's preference |
| Devcontainer target | mcr.microsoft.com/devcontainers/base:debian | Pre-baked dev tools, non-root vscode user, works with VSCode out-of-the-box |
| CUDA/GPU workloads | nvidia/cuda:12.x-runtime-ubuntu24.04 | GPU support; use -devel if you're building GPU code |
| ML/data science | debian:12-slim or a micromamba base | Avoid alpine — scikit-learn, numpy, torch all assume glibc |
| Extreme size constraints | gcr.io/distroless/cc-debian12 (runtime only) | Static or carefully-copied binaries only; mise belongs in the builder stage, not here |
| You really want alpine | alpine:3.20 with caveats (see below) | Only if you know what you're doing |
alpine caveatAlpine uses musl libc instead of glibc. This matters because:
node-gyp builds will need apk add --no-cache python3 make g++.apk add build-base.Rule of thumb: if the image will build code, avoid alpine. If the image will only run a statically-linked Go/Rust binary, alpine is fine for the runtime stage.
For the builder stage, use debian/ubuntu even if the runtime is alpine. Multi-stage lets you mix them:
FROM debian:12-slim AS builder
# ... mise install + build ...
FROM alpine:3.20 AS runtime
COPY --from=builder /workspace/target/release/myapp /usr/local/bin/myapp
# Only works if myapp is statically linked (Go, `cargo build --target x86_64-unknown-linux-musl`, etc.)
debian:12-slim is the defaultdebian:12's ~120MB).apt, which you need for system libs (libssl-dev, libpq-dev, libsqlite3-dev, etc.).mcr.microsoft.com/devcontainers/base:debian for devcontainersvscode user pre-created (UID 1000).git, curl, sudo, zsh, and common dev CLIs already installed.ghcr.io/devcontainers/features/* feature system.nvidia/cuda for GPU-runtime for production inference, -devel for training / building CUDA kernels.12.4.1) not just major — torch wheels are picky.| Base | Size | Notes |
|---|---|---|
gcr.io/distroless/static | ~2MB | Static binaries only |
gcr.io/distroless/cc-debian12 | ~20MB | Static or carefully-copied C deps |
alpine:3.20 | ~8MB | Musl caveat applies |
debian:12-slim | ~80MB | Recommended default |
ubuntu:24.04 | ~80MB | Essentially the same |
mcr.microsoft.com/devcontainers/base:debian | ~500MB | Worth it for devcontainers |
nvidia/cuda:12.4.1-runtime-ubuntu24.04 | ~3GB | Unavoidable for GPU |
Don't optimize image size prematurely. A 500MB base that boots and builds cleanly is always better than a 20MB base where half your tools don't work.
mise-docker-patterns — the canonical multi-stage Dockerfile.mise-docker-multistage — why to split builder and runtime.mise-host-vs-mise-tools — which things belong in apt vs mise. The short version: compilers and system libs = apt; language runtimes = mise.