Docker Client Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 34: | Line 34: | ||
==Lifecycle== | ==Lifecycle== | ||
:<span id='run'></span>[[docker run|run]] | :<span id='run'></span>Run a container: [[docker run|run]] | ||
:<span id='start'></span>[[docker start|start]] | :<span id='start'></span>[[docker start|start]] | ||
:<span id='stop'></span>[[docker stop|stop]] | :<span id='stop'></span>[[docker stop|stop]] | ||
Revision as of 01: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
Lifecycle
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