Docker Client Operations: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 77: Line 77:
If the image has a shell, it can be run in interactive mode and explored:  
If the image has a shell, it can be run in interactive mode and explored:  


   [[docker run]] -it <''image-id''|''name''> sh
   [[docker run]] --rm -it <''image-id''|''name''> sh


While the container is running, the image can be exported into a TAR file system with [[docker export]] and explored off-line.
While the container is running, the image can be exported into a TAR file system with [[docker export]] and explored off-line.

Revision as of 23:22, 24 January 2018

External

Internal

Commands

build create cp rm
pull push rmi
tag

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 Introspection and Manipulation

Explore an Image

If the image has a shell, it can be run in interactive mode and explored:

 docker run --rm -it <image-id|name> sh

While the container is running, the image can be exported into a TAR file system with docker export and explored off-line.

Container Lifecycle Operations

Container Introspection

Interaction with a Running Container

Security

Scenarios

Docker Client Scenarios

Troubleshooting