Docker Client Operations: Difference between revisions

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


<font color=red>'''TODO''': how is a docker instance configured with specific [[Docker Concepts#Image_Registry_Operations|registries]]?</font>
<font color=red>'''TODO''': how is a docker instance configured with specific [[Docker Concepts#Image_Registry_Operations|registries]]?</font>
* <span id='Pull_an_Image_from_Registry'></span>Pull an image or a repository from a registry and place it in the local registry: [[docker pull#Overview|docker pull]]


=Scenarios=
=Scenarios=


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

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

Container Introspection

Interaction with a Running Container

Image Registry Operations

TODO: how is a docker instance configured with specific registries?

  • Pull an image or a repository from a registry and place it in the local registry: docker pull

Scenarios

Docker Client Scenarios