Disconnected Environments in a Connected World
summary
Most modern tools assume always-on internet so deploying into air-gapped networks forces concrete fixes: bundle full dependency trees (Hopper ecosystem creates sbom-driven bundles and Dropper deploys them), burn multi-DVD images or use a data diode, run self-hosted GitLab/Mattermost and private OCI registries, and use Zarf to pack images (it even pages across DVDs). Real problems include missing transitive Python deps that cost a hackathon two days, NTP/time drift breaking certs, and an offline LLM proving immediately useful.
AI-written summary · about
chapters (12)
- 0:00Disconnected environments intro
- 2:12Air gap definitions
- 4:41Developing in air-gapped systems
- 7:27Data transfer in secure envs
- 10:39Time sync in isolated nets
- 12:22Proxy and DNS in air gaps
- 16:14Hardening secure systems
- 17:40Building software offline
- 20:30Air-gapped dev tools
- 26:11Advice for maintainers
- 34:46Advocating air-gap tooling
- 37:16Distributed systems in air gaps
related talks
43mHow Software Is Deployed on Submarines
30mOffline IoT - Building Resilient Connected Devices without the Internet
36mContinuous Deployment of IoT Sensors
24mCan't Touch This!: When Things go Wrong With an Appliance
30mBuilding Linux Distributions for Fun and Profit
37mContinuous Delivery for Embedded Systems
27mLitterbox: Somewhat Isolated Development Environments
32mEvent-Driven Infrastructure: Autonomous Operation and Unreliable Networks