Docker Client Operations: Difference between revisions

From NovaOrdis Knowledge Base
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

Internal

Commands

build create cp rm
ps run stop rm
pull push rmi
tag

Installation Verification

Docker 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

Image Operations

Registry Operations

Image Introspection and Manipulation

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

Interaction with a Running Container

Container Introspection

Network

Network Operations

Security

Scenarios

Docker Client Scenarios

Troubleshooting