TL;DR: Teleport describes saved container work as surviving base-image updates while still inheriting patch changes. Container governance has to account for which paths stay mutable, which are rebuilt, and which state can safely be forked.
Editorial analysis by NHI Mgmt Group, based on content published by Teleport: “Phases: Git for container filesystems, or, what I built after leaving CNCF buildpacks.io”.
Key questions
Q: How should teams separate persistent workspace state from rebuilt layers?
A: Persistent workspace state should live in dedicated volumes or mounted directories, while rebuilt layers stay immutable and disposable in the image or container filesystem.
Q: What is the difference between snapshot layers and rebuild layers?
A: Snapshot layers capture a filesystem point in time, usually for storage, backup or clone purposes, while rebuild layers are produced again from a definition such as a container image or build recipe.
Q: How do container image layers differ from Git commits?
A: Container image layers are addressable filesystem snapshots, not a linear history of every change.
Practitioner guidance
- Define filesystem ownership boundaries Separate durable workspace paths from rebuilt runtime paths before you adopt any forkable container model, so state cannot drift into the wrong lifecycle.
- Inventory copied and persisted artefacts Track which files, credentials, and configuration items enter containers through copy phases or interactive writes, then treat them as governed state.
- Set explicit rebuild scopes Limit which directories and dependencies can be refreshed automatically, and document the paths that must remain outside the rebuild path.
Bottom line: Phases addresses a real container governance problem: how to let work persist without letting stale state, copied artefacts, or old dependencies linger unchecked.
Glossary terms: Container Image Layer, Rebase, OverlayFS, Pivot Root
What's in the full article
Teleport's full blog post covers the implementation detail this post intentionally leaves at the architectural level:
- How Phases maps rebuild, snapshot, and copy responsibilities into separate filesystem lifecycles
- How the Beams runtime uses Kubernetes, Kata Containers, and Cloud Hypervisor to isolate builds
- How the builder uses OverlayFS, pivot_root, and cgroup freezing to capture state safely
- How registry metadata updates drive rebasing without forcing a full rebuild of every layer
👉 Read Teleport's blog post on Phases for container filesystem state and rebasing →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →