Docker Registry Operations: Difference between revisions
Jump to navigation
Jump to search
(→Start) |
|||
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
"Docker Registry" in this context refers to the image published by Docker, which instantiates as [[Docker_Concepts#Exposing_the_Content_of_the_Local_Image_Registry_over_TCP_with_Docker_Registry|a container that exposes the content of the local registry over TCP]]. | "Docker Registry" in this context refers to the image published by Docker, which instantiates as [[Docker_Concepts#Exposing_the_Content_of_the_Local_Image_Registry_over_TCP_with_Docker_Registry|a container that exposes the content of the local registry over TCP]]. Note that by default the Docker Registry container starts with HTTP support only, so all other Docker servers that use it must be configured to allow it as an "insecure registry", with --insecure-registry as described {{/etc/sysconfig/docker#--insecure-registry|here}}. | ||
=Start= | =Start= | ||
docker run -d -p 5000:5000 --name registry registry:2 | docker run -d -p 5000:5000 --name registry registry:2 | ||
Revision as of 22:42, 19 April 2018
Internal
Overview
"Docker Registry" in this context refers to the image published by Docker, which instantiates as a container that exposes the content of the local registry over TCP. Note that by default the Docker Registry container starts with HTTP support only, so all other Docker servers that use it must be configured to allow it as an "insecure registry", with --insecure-registry as described Template:/etc/sysconfig/docker.
Start
docker run -d -p 5000:5000 --name registry registry:2