Docker Client Operations: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 52: Line 52:
* <span id='Image_History'></span>Obtain image history: [[docker history]]
* <span id='Image_History'></span>Obtain image history: [[docker history]]
* <span id='Image_Save'></span>Save an image into a TAR archive: [[docker save]]
* <span id='Image_Save'></span>Save an image into a TAR archive: [[docker save]]
* <span id='load'></span>Load an image from a TAR archive[[docker load|load]]
* <span id='load'></span>Load an image from a TAR archive: [[docker load|load]]
* <span id='Export_the_Filesystem'></span>Export a container's filesystem into a TAR file: [[docker export]]
* <span id='Export_the_Filesystem'></span>Export a container's filesystem into a TAR file: [[docker export]]
* <span id='import'></span>Create a new image from a TAR archive: [[docker import|docker import]]
* <span id='import'></span>Create a new image from a TAR archive: [[docker import|docker import]]

Revision as of 18: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

Registry Operations

Image Manipulation

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

Container Introspection

Interaction with a Running Container

Scenarios

Docker Client Scenarios