-
Notifications
You must be signed in to change notification settings - Fork 547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Include container image manifests and layers in sosreport #3796
Comments
Sounds reasonable - what environments/runtimes are you looking for?
EDIT: and/or |
We are interested in containerd. But other runtimes may be interested in it as well. Some hierarchy of layers and all the manifests would be great to have in the report. cc: @samuelkarp to advice on the best way to collect this for containerd |
Adds collection of container image layers for the docker and podman plugins via the `history` and `tree` subcommands repsectively. Resolves: sosreport#3796 Signed-off-by: Jake Hunsaker <[email protected]>
Adds collection of container image layers for the docker and podman plugins via the `history` and `tree` subcommands repsectively. Resolves: sosreport#3796 Signed-off-by: Jake Hunsaker <[email protected]>
Adds collection of container image layers for the docker and podman plugins via the `history` and `tree` subcommands repsectively. Related: sosreport#3796 Signed-off-by: Jake Hunsaker <[email protected]>
Adds collection of container image layers for the docker and podman plugins via the `history` and `tree` subcommands repsectively. Related: #3796 Signed-off-by: Jake Hunsaker <[email protected]>
Seems like this was closed by mistake. This hasn't been implemented by Containerd. |
Yep, mistakenly closed. I had updated the tag to |
Currently, sosreport does not capture detailed information about container images running on a node. This can make it difficult to troubleshoot issues with containerized applications. Requesting feature to dump all manifests and layers for images on a Node in sosreport.
The text was updated successfully, but these errors were encountered: