Docker Client Operations: Difference between revisions

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


* [[docker - Start a Container Automatically|Start a Container Automatically]]
* [[docker - Start a Container Automatically|Start a Container Automatically]]
* [[Docker Attach to a Running Container|Attach to a Running Container]]
* [[Docker_exec#Attach_to_a_Running_Container|Attach to a Running Container]]


=Scenarios=
=Scenarios=


{{Internal|Docker Client Scenarios|Docker Client Scenarios}}
{{Internal|Docker Client Scenarios|Docker Client Scenarios}}

Revision as of 07:01, 26 November 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

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

Lifecycle

Create and run a new container: run
Stop a container: stop
Start a previously stopped container: start
Remove a container: rm

Image Management

List images in the local repository: images
Remove images from the local repository: rmi

Executions

exec

Other

build
import
load
update

Installation Verification

Docker Installation Verification

Search for Images

Use "search" to look into Docker hub for publicly available images:

docker search <term>

A different repository can be specified as follows:

docker search registry.access.redhat.com/rhel7.4

Recipes

Scenarios

Docker Client Scenarios