How can I track changes in container images more effectively?

0
0
Asked By CuriousCoder42 On

Hey folks! I've been working a lot with CI images and sometimes I really need to dig into what changed in a container layer, not just the files added or deleted, but the actual content changes. I found that while Dive is a solid tool for checking layer status, it doesn't give full file differences. That's why I created oci2git, which turns OCI-compatible container images into a Git repository where each layer shows up as a commit. With it, I can run 'git diff' between layers, use VSCode or lazygit to explore changes, and even track filesystem history like regular Git commands. I'm curious though—how do you all usually inspect images? Are there any other methods like Dive or manual tarballing that you prefer? Would love your feedback!

4 Answers

Answered By FutureDevOpsStar On

This is such a clever use of Git! I think your tool could become really popular in the DevOps community!

Answered By TechieTom On

This sounds awesome! I can't wait to give it a try. Thanks for sharing your project!

Answered By VSCodeNinja On

Great concept! Can you explain how you actually use VS Code for diffs? I know comparing files is possible, but how do you handle folders?

Answered By DevDude88 On

I really like the idea! It would be neat if you could add a feature to see changes between two different images. Maybe something like 'oci2git diff image1 image2' could work?

CuriousCoder42 -

I love that suggestion! It would definitely expand the tool's usefulness. Can you share more about how you envision that working?

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.