The Environments Inside Your Containers
summary
Claims Dockerfile workflows cause unreproducible, large, insecure images and shows Flox as a concrete replacement that produces lean, auditable artifacts. Demonstrations include generating a reproducible lockfile, building images from a runtime dependency closure instead of opaque layers, activating exact dev environments locally, and then running Flox containerize to emit minimal OCI images. Examples show multi-package orgs shrinking dozens or hundreds of ad‑hoc images into small reusable blocks and images that actually rebuild identically.
AI-written summary · about
chapters (11)
- 0:00Container environments and EU regulations
- 1:54Building containers today
- 6:52Container image management challenges
- 11:30Developer pain points with containers
- 16:13History of container technologies
- 21:39Simpler container workflows
- 24:09Nyx and dependency management
- 30:13Docker images with Nyx
- 34:08Nyx evolution and Flux
- 38:22Local dev environments with Flux
- 43:41Containerizing with Flux
related talks
33mDocker Container Lifecycles – Problem or Opportunity?
57mKiller Docker Workflows for Development
16mBest Practices for Container Image Promotion Pipelines
38mFrom Docker'fail to Dockerfile.. a true story!
34mDefence Against the Docker Arts
01h 14mTutorial: Workshop: Developing as a Team for Kubernetes With Nix and Flox
26mContainerization crossroads: Experiences-Experiments-Expectations
51mProduction level Docker