Docker Client Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 101: | Line 101: | ||
* [[Docker_exec#Attach_to_a_Running_Container|Attach to a Running Container]]: <span id='exec'></span>[[docker exec|docker exec]] | * [[Docker_exec#Attach_to_a_Running_Container|Attach to a Running Container]]: <span id='exec'></span>[[docker exec|docker exec]] | ||
* <span id='update'></span>[[docker update|docker update]] | * <span id='update'></span>[[docker update|docker update]] | ||
* <span id='attach'></span>[[docker attach|docker attach]] | * Attach the local standard input, output, and error streams to a running container: <span id='attach'></span>[[docker attach|docker attach]] | ||
* Copy files [[docker cp]]. | * Copy files [[docker cp]]. | ||
Revision as of 03:45, 1 May 2018
External
- Docker Cheat Sheet: https://github.com/wsargent/docker-cheat-sheet
Internal
Commands
| build | create | cp | rm |
| ps | run | stop | rm |
| pull | push | rmi | |
| tag |
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
- Resource statistics for running containers docker stats.
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?
- docker tag
Image Introspection and 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 --rm -it <image-id|name> bash|sh
While the container is running, the image can be exported into a TAR file system with docker export and explored off-line.
Determine the Command that Launches the Process to Be Executed in the Container
docker inspect --format '{{.Config.Cmd}}' <image-id>
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
- Restart a container: docker restart
- Remove a container: docker rm
- Start a Container Automatically
Interaction with a Running Container
- Attach to a Running Container: docker exec
- docker update
- Attach the local standard input, output, and error streams to a running container: docker attach
- Copy files docker cp.
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
- Resource statistics for running containers docker stats.