Hey folks! I'm diving into the world of CI images and build debugging, and I'm really curious about how to see the nitty-gritty details of what's changed in a container layer. For instance, I don't just want to know what files are added or deleted; I want to see the actual content changes as well. I've been using Dive, which is a solid tool, but it primarily shows file names and their statuses without going into the details. That's why I developed oci2git, a tool that turns any OCI-compatible container image into a Git repository. Each image layer is represented as a commit, which allows you to do things like:
- Utilize `git diff` to compare layers and inspect content changes directly, even in tools like VSCode or lazygit.
- Leverage `git blame` to track down which layer made changes to a file.
- Navigate through the entire filesystem history with standard Git commands.
This has proven invaluable for auditing and in-depth image analysis. I'm eager to get your thoughts and hear how you all handle image inspections—are you using Dive, manual tarballing, or something else?
4 Answers
That sounds really neat! I’m definitely going to check out oci2git. Thanks for sharing it!
Cool concept! How do you use VSCode for diffs afterward? I know it allows file comparisons, but can it handle folder comparisons, too?
Amazing idea to leverage git for image changes! This project could really become a go-to tool for the DevOps community!
It would be awesome to have a feature that allows you to compare changes not just in a single image, but across different images too. Like a command that runs `oci2git diff image1 image2` to show the differences in a couple of commits—what do you think?
Related Questions
Convert Json To Xml
Bitrate Converter
JavaScript Multi-line String Builder
GUID Generator
GUID Validator
Convert Json To C# Class