Docker Client Operations: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 68: Line 68:


{{Internal|Docker Client Scenarios|Docker Client Scenarios}}
{{Internal|Docker Client Scenarios|Docker Client Scenarios}}
=TODO=
<font color=red>
==Queries==
: Look at container's logs [[docker logs|logs]]
: Changes introduced in the container's file system [[docker diff]]
==Executions==
:<span id='exec'></span>[[docker exec|exec]]
==Other==
:<span id='import'></span>[[docker import|import]]
:<span id='load'></span>[[docker load|load]]
:<span id='update'></span>[[docker update|update]]
</font>

Revision as of 02:36, 5 December 2017

External

Internal

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

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

Otherwise it can be exported into a TAR file system with docker export and explored.

Container Lifecycle Operations

Scenarios

Docker Client Scenarios

TODO

Queries

Look at container's logs logs
Changes introduced in the container's file system docker diff

Executions

exec

Other

import
load
update