Docker Client Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
| [[docker build|build]] || [[docker create|create]] || [[docker cp|cp]] || [[docker rm|rm]] | | [[docker build|build]] || [[docker create|create]] || [[docker cp|cp]] || [[docker rm|rm]] | ||
|- | |- | ||
| [[docker pull|pull]] || [[docker rmi|rmi]] | | [[docker pull|pull]] || [[docker push|push]] || [[docker rmi|rmi]] | ||
|} | |} | ||
Revision as of 04:08, 18 January 2018
External
- Docker Cheat Sheet: https://github.com/wsargent/docker-cheat-sheet
Internal
Commands
| build | create | cp | rm |
| pull | push | rmi |
Installation Verification
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
Info
- Server and client version docker version
- System-wide info docker info
- Low level metadata about an image or container docker inspect
Image Operations
Registry Operations
- Search Docker Hub or other registries: docker search
- List images in the local registry: docker images
- Remove images from the local registry: docker rmi
- Pull an image or a repository from a registry and place it in the local registry: docker pull
- Push an image or a repository to a registry: docker push
- TODO: how is a docker instance configured with specific registries?
Image Manipulation
- Build an image: docker build
- Obtain low-level metadata about an image: docker inspect
- Obtain image history: docker history
- Save an image into a TAR archive: docker save
- Load an image from a TAR archive: docker load
- Export a container's filesystem into a TAR file: docker export
- Create a new image from a TAR archive: docker import
- Modifying an existing Image
- Copy Files In and Out of a Container
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
While the container is running, the image can be exported into a TAR file system with docker export and explored off-line.
Container Lifecycle Operations
- List containers (running or otherwise): docker ps
- Create and run a new container: docker run
- Stop a running container: docker stop
- Start a previously stopped container: docker start
- Remove a container: docker rm
- Start a Container Automatically
Container Introspection
- Low-level information about a container: docker inspect
- Look at container's logs docker logs
- Explore changes introduced in the container's file system docker diff