Files
container.training/slides/swarm/hostingregistry.md
Jerome Petazzoni fadecd52ee Replace registry:2 with registry
registry used to be registry v1, but now it defaults to v2.
We can therefore drop the tag.
2018-09-28 18:36:29 -05:00

881 B

Hosting our own registry

  • We need to run a registry container

  • It will store images and layers to the local filesystem
    (but you can add a config file to use S3, Swift, etc.)

  • Docker requires TLS when communicating with the registry

    • unless for registries on 127.0.0.0/8 (i.e. localhost)

    • or with the Engine flag --insecure-registry

  • Our strategy: publish the registry container on port 5000,
    so that it's available through 127.0.0.1:5000 on each node

Deploying the registry

  • We will create a single-instance service, publishing its port on the whole cluster

.exercise[

  • Create the registry service:

    docker service create --name registry --publish 5000:5000 registry
    
  • Now try the following command; it should return {"repositories":[]}:

    curl 127.0.0.1:5000/v2/_catalog
    

]