Docker Client Operations: Difference between revisions
Jump to navigation
Jump to search
Line 36: | Line 36: | ||
==Lifecycle== | ==Lifecycle== | ||
:<span id='run'></span> | :<span id='run'></span>Create an run a new container: [[docker run|run]] | ||
:<span id='stop'></span>Stop a container: [[docker stop|stop]] | :<span id='stop'></span>Stop a container: [[docker stop|stop]] | ||
:<span id='start'></span>[[docker start|start]] | :<span id='start'></span>Start a previously stopped container: [[docker start|start]] | ||
==Executions== | ==Executions== |
Revision as of 02:49, 20 November 2017
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
- images
- 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 an run a new container: run
- Stop a container: stop
- Start a previously stopped container: start
Executions
Other
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