Docker Client Operations: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 80: Line 80:
   [[docker run]] -it <''image-id''|''name''> sh
   [[docker run]] -it <''image-id''|''name''> sh


Otherwise it can be exported into a TAR file system and explored:
Otherwise it can be exported into a TAR file system with <tt>[[docker export]]</tt> and explored.


=<span id='Lifecycle'></span>Container Lifecycle Operations=
=<span id='Lifecycle'></span>Container Lifecycle Operations=

Revision as of 02:08, 5 December 2017

External

Internal

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

Commands

Info

System-wide info docker info

Queries

ps
Low-level information about a container: inspect
version
Look at container's logs logs
Changes introduced in the container's file system docker diff

Executions

exec

Other

import
load
update

Installation Verification

Docker Installation Verification

Recipes

Scenarios

Docker Client Scenarios

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