Let's talk a bit more about container images.
When you run a container, the image
is pulled from the registry.
And after pulling, the image is stored somewhere
in the home directory of the user that runs the container.
And we have already seen if 20 users
are running the same container, the image is stored 20 times.
You can use Popman images or Popman image LS
for a list of current images.
Images are not automatically removed.
So you should check every now and then
if you still need all of your images.
And if you don't, then you can use Popman image RM
to manually remove images.
Or a very nice command is Popman image prune,
which will remove unused images automatically.
Let me show you.
So when I use Popman images,
there we can see all the images.
And well, these are images that I like to have.
So I'm not going to remove them or prune them or whatever.
But I might want to do a Popman image minus minus help.
Popman images is an interface that allows you
to work with images.
And minus minus help is showing everything
that you can do with these images.
Minus minus help in Popman works at every level
if you need more detail.
Now, let me use Popman image inspect.
On NGINX and pipe that through the LESH utility
so that you can see what is going on.
So what do we see?
Well, we see the exposed port.
We see some environment variables.
We see the entry point.
We see the default command.
And you might find other information as well
that is interesting.
Oh, this is an ARM64 image.
So that is why it works in my virtual machine
on MacBook with Silicon.
And much more information about the image can be found here.
In some cases, you'll need this information
to run your container successfully.
We'll talk about it later.