container-diff
container-diff copied to clipboard
container-diff: Diff your Docker containers
## One particular docker image can not be inspected. ### Expected behavior Getting info. ### Actual behavior Nothing is returned. ``` sudo container-diff analyze cmssw/docker-lxr:v0 --type=history --type=file --type=size --type=rpm --type=pip...
Consider image with `python-3.6` inside and additional pip packages installed via requirements file (via `setup.py`). your app includes `requirements.txt` with following packages: ``` graphitesend future ``` When you perform `container-diff...
The standard docker image format looks like something like ```bash 80484ae1c6bf4188800d727446232d1f0f03ae27104878c83d21794291283bf0/ 80484ae1c6bf4188800d727446232d1f0f03ae27104878c83d21794291283bf0/VERSION 80484ae1c6bf4188800d727446232d1f0f03ae27104878c83d21794291283bf0/json 80484ae1c6bf4188800d727446232d1f0f03ae27104878c83d21794291283bf0/layer.tar 8176e035de519557279f4a0a46d8b72bbab71565867311af57ae00381ca18314.json b02b500eecbef83c9c566b28ae72270d5cf4d38fb37692c436d603a17f41dd0e/ b02b500eecbef83c9c566b28ae72270d5cf4d38fb37692c436d603a17f41dd0e/VERSION b02b500eecbef83c9c566b28ae72270d5cf4d38fb37692c436d603a17f41dd0e/json b02b500eecbef83c9c566b28ae72270d5cf4d38fb37692c436d603a17f41dd0e/layer.tar manifest.json repositories ``` But there's an alternate format, where the layer...
Currently there is no integration test that checks that no --types passed results in all differs being used. This allowed https://github.com/GoogleCloudPlatform/container-diff/pull/85 to get through.
We should try and set up some infrastructure to track things like downloads, 7-day active users, etc. Monitoring downloads will be related to where the release is stored and won't...
currently when diffing layers of images, container-diff essentially requires layers to in the same order and have the same number of layers for the diff to be meaningful. A single...
For some files, it looks like the file analyzer is incorrectly computing the sizes of the files. ``` ➜ docker run -it --entrypoint=/bin/bash gcr.io/kaniko-test/kaniko-dockerfile_test_user_run testuser@255b1e956c6e:/$ ls -la /var/log ... -rw-r--r--...
- stdout should have machine parseable output - stderr should have logs (when enabled) and user visible status output - return codes should be 0 unless there is an error...
This is meant to serve as a discussion point for refactoring differs and preppers. The current design is roughly: 1. Preppers unpack images from a variety of sources (registry, tarball,...