8f6a0243f4
First, make podman diff accept optionally a second argument. This allows the user to specify a second image/container to compare the first with. If it is not set the parent layer will be used as before. Second, podman container diff should only use containers and podman image diff should only use images. Previously, podman container diff would use the image when both an image and container with this name exists. To make this work two new parameters have been added to the api. If they are not used the previous behaviour is used. The same applies to the bindings. Fixes #10649 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
1.5 KiB
% podman-diff(1)
NAME
podman-diff - Inspect changes on a container or image's filesystem
SYNOPSIS
podman diff [options] container|image [container|image]
DESCRIPTION
Displays changes on a container or image's filesystem. The container or image will be compared to its parent layer or the second argument when given.
The output is prefixed with the following symbols:
| Symbol | Description |
|---|---|
| A | A file or directory was added. |
| D | A file or directory was deleted. |
| C | A file or directory was changed. |
OPTIONS
--format
Alter the output into a different format. The only valid format for podman diff is json.
--latest, -l
Instead of providing the container name or ID, use the last created container. If you use methods other than Podman to run containers such as CRI-O, the last started container could be from either of those methods. (This option is not available with the remote Podman client)
EXAMPLE
$ podman diff container1
A /myscript.sh
$ podman diff --format json myimage
{
"changed": [
"/usr",
"/usr/local",
"/usr/local/bin"
],
"added": [
"/usr/local/bin/docker-entrypoint.sh"
]
}
$ podman diff container1 image1
A /test
SEE ALSO
podman(1), podman-container-diff(1), podman-image-diff(1)
HISTORY
August 2017, Originally compiled by Ryan Cole rycole@redhat.com