Docker Client Operations: Difference between revisions
Jump to navigation
Jump to search
Line 69: | Line 69: | ||
{{Internal|Docker_Concepts#Docker_Image_Operations|Docker Concepts - Images}} | {{Internal|Docker_Concepts#Docker_Image_Operations|Docker Concepts - Images}} | ||
== | ==== | ||
* <span id='Search_for_Images'></span>Search Docker Hub or other registries: [[docker search]] | |||
==List Images== | ==List Images== |
Revision as of 00:39, 5 December 2017
External
- Docker Cheat Sheet: https://github.com/wsargent/docker-cheat-sheet
Internal
Running the Client
On the Same Host as the Server
In order to connect to the docker server over the Unix socket, the user running the client must have permissions to do so:
[testuser@docker-server ~]$ ls -al /var/run/docker.sock srw-rw----. 1 root docker 0 Apr 25 16:00 /var/run/docker.sock
One way to do that is to make the user a member of "docker" group:
usermod -G docker testuser
From a Remote Host
Commands
Info
- System-wide info docker info
Queries
- ps
- Low-level information about a container: inspect
- version
- Look at container's logs logs
- Changes introduced in the container's file system docker diff
Executions
Other
Installation Verification
Recipes
Scenarios
Image Operations
==
- Search Docker Hub or other registries: docker search
List Images
List images in the local repository:
docker images
Remove an Image
Remove images from the local repository:
docker rmi
Pull an Image from Registry
Pull an image or a repository from a registry:
docker pull
- Build an image: docker build
Explore an Image
If the image has a shell, it can be run in interactive mode and explored:
docker run -it <image-id|name> sh
Image History
docker history
Export the Filesystem
docker export
Container Lifecycle Operations
Create and Run a New Container
Create and run a new container:
docker run
Stop a Container
Stop a container:
docker stop
Start a Previously Stopped Container
Start a previously stopped container:
docker start
Remove a Container
Remove a container
docker rm