Steiger: Oci-Native Builds for Docker, Bazel, and Nix with Direct Registry Push
Posted4 months ago
github.comDevopsstory
informativepositive
Debate
20/100
OciContainersDependency_managementDevops
Key topics
Oci
Containers
Dependency_management
Devops
Discussion Activity
Light discussionFirst comment
N/A
Peak period
1
Start
Avg / period
1
Key moments
- 01Story posted
Aug 27, 2025 at 5:58 PM EDT
4 months ago
Step 01 - 02First comment
Aug 27, 2025 at 5:58 PM EDT
0s after posting
Step 02 - 03Peak activity
1 comments in Start
Hottest window of the conversation
Step 03 - 04Latest activity
Aug 27, 2025 at 5:58 PM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45045846Type: storyLast synced: 11/18/2025, 12:11:17 AM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
The TAR bottleneck: Skaffold forces Bazel to export OCI images as TAR files, then imports them back into Docker. This is slow and wasteful
Cache invalidation: Skaffold's custom caching layer often conflicts with the sophisticated caching that build systems like Bazel and Nix already provide.
Currently supports:
Docker BuildKit: Uses docker-container driver, manages builder instances
Bazel: Direct OCI layout consumption, skips TAR export entirely
Nix: Works with flake outputs that produce OCI images
Ko: Native Go container builds
Still early days - we're planning file watching for dev mode and (basic) Helm deployment just landed!