This command downloads images. You can pull images from repositories inside of remote registries. By default, images are pulled from @Docker Hub.
This command will pull images tagged as `latest` by default.
2/ docker image ls
This command lists all of the images stored in your @Docker hosts local image cache. You can use the `--digest` option to get the SHA256 hash code of the image as well.
3/ docker image inspect
A powerful command that allows you to see all the nitty-gritty detail of an image.
The layer data, the metadata, all of it.
4/ docker manifest inspect
With this command you can inspect the manifest list of any image stored on @Docker hub.
For example, if you wanted to see the manifest list of the ubuntu image you can type: `docker manifest inspect ubuntu` to see it.
Side bar: a manifest is a list of image layers that is created by specifying one or more image names.
A @Docker image starts with a base layer, and as new changes are made and new content is added, new layers are added on top.
An image is a combo of all layers stack in order.
5/ docker image rm
You use this command to delete an image.
Note: if an image layer is shared by more than one image, that layer won't be deleted until all images that reference it have been deleted.
Also, you can't delete an image that is associated with a running container
Bonus:
Use `$ docker image rm $(docker image ls -q) -f` to delete all imaged on a @Docker host.
If you found this helpful, be sure to go back to the top and share it with your friends.
Smash that follow on my profile and hit the bell notification so you don't miss out on posts while you're at it.
You use this command to start a new @Docker container.
It accepts an image and a command as its arguments. The image is used to create the container. The command is the application the container will run when it starts.
For example, running the following command will start an ubuntu container and run the bash shell
docker container run -it ubuntu /bin/bash
Oh yea, the -it runs an interactive terminal. It attaches the containers terminal to your terminal.
A hiring manager isn’t going to be able to open your head, peek inside your brain, and verify if you know how to do this thing or that, or how well you understand this, that or the other.
That’s why you need to do a project.
2/ You need experience to get a job
But that doesn’t mean you need a job to get experience.
Data is everywhere.
You don’t need to be in a job at a company to get access to data.
If you know where to look and how to search for it, you’ll quickly see that it is everywhere.