![]() ![]() This example shows the images I have been using since the first article: $ podman image lsĭocker.io/library/wordpress latest 054741915cf1 6 weeks ago 629 MBĭocker.io/library/mysql latest bbf6571db497 6 weeks ago 521 MBĭocker.io/library/httpd latest ea28e1b82f31 6 weeks ago 148 MB However, the Podman command-line interface (CLI) alone can help you gather some of this information. In certain scenarios, it might be useful to use more in-depth inspection tools like Skopeo, which allows you to inspect "a remote image showing its properties including its layers, without requiring you to pull the image to the host." You could also check the image's Dockerfile to get update information. Tracking these changes allows you to understand their impact on your environment. Inspect images before updatingīefore updating any images, it's important to understand what changes from one image version to another. To follow along with this article, first run the shell scripts I used in the " Setting things up" section of the first article in this series. Keeping running containers and pods current with the most up-to-date image changes is important. This article demonstrates how to update container images. How Podman can extract a container's external IP address.How to use Podman to get information about your containers.Create fast, easy, and repeatable containers with Podman and shell scripts.A practical introduction to container terminologyīefore reading this article, make sure you've read the first three parts:.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |