Introduction
Easy to use Container Inspector, works with CI.
- 1. Create an API Key in your Settings.
- 2. Log into warpdive-cli and paste your API Key when prompted
npx
warpdive login
- You can then simply push images to your account
npx
warpdive push ubuntu:latest
Note: You may need to pull the image you’re trying to push to warpdive first. In this
example: docker pull ubuntu:latest
will fetch the image locally so it can be used.
You can also target container images you're working on. For instance with a directory containing
a Dockerfile
npx
warpdive build . --wd-project example-image
This will send the file warpdive generates to your account.
Read the command line help to learn more
npx
warpdive -h
Warpdive supports Docker and Podman
Local Export
You can also inspect containers completely offline.
npx
warpdive export . --wd-export example-image
This will create a .warpdive file locally which you can inspect at warpdive.xyz/viewer. The file will be read in your browser and not be sent anywhere.
.warpdive File Format
Warpdive when ‘building’ a container reads the layers and their contents in the container image.
A .warpdive file is a snapshot of information, specifically,
the file hierarchy in each layer, file sizes, permissions and metadata such as file names etc. It does
not store the actual files that were added/removed, just the information about what files were added/removed.
This makes warpdive suitable for CI. Where you want to know what happened during a build, why a layer isn't caching or what files are added/removed at each layer.
To report any issues, please submit an issue at github.com/gvkhna/warpdive/issues