LINKED LIST [txt mode] ▸ Broken by default: why you should avo...

home explore | log in

Broken by default: why you should avoid most Dockerfile examples

pythonspeed.com · first added by @afreshcup · 2026-09-30 · 1 upvotes

log in to save, upvote or flag this.

─── In 0 lists ─────────────────────────────────────────

(not in any lists yet)

─── Discussions ────────────────────────────────────────

* Simple Dockerfile examples are often broken by default

461 pts · 157 comments · node

* Simple Dockerfile examples are often broken by default (2019)

10 pts · 4 comments · node

─── From the discussion ────────────────────────────────

* GitHub - hadolint/hadolint: Dockerfile linter, validate inline bash, written in Haskell

github.com · node

* Why Your Dockerized Application Isn’t Receiving Signals

hynek.me · node

* Optimising Docker Layers for Better Caching with Nix - Graham Christensen

grahamc.com · node

* GitHub - docker/docker-bench-security: The Docker Bench for Security is a script that checks for dozens of common best-practices around deploying Docker containers in production.

github.com · node

* Build packages as wheels, then install in small container.

gist.github.com · node