mirror of
https://github.com/jpetazzo/container.training.git
synced 2026-07-28 01:01:12 +00:00
8decf1852f
We now have two clean classes: btp-manual and btp-auto Exclude one or the other depending on whether you want to show the full process of building and pushing images, or if you want to shortcut and use stack files directly.
40 lines
949 B
Markdown
40 lines
949 B
Markdown
# Hosting our own registry
|
|
|
|
- We need to run a `registry:2` container
|
|
<br/>(make sure you specify tag `:2` to run the new version!)
|
|
|
|
- It will store images and layers to the local filesystem
|
|
<br/>(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,
|
|
<br/>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:
|
|
```bash
|
|
docker service create --name registry --publish 5000:5000 registry:2
|
|
```
|
|
|
|
- Now try the following command; it should return `{"repositories":[]}`:
|
|
```bash
|
|
curl 127.0.0.1:5000/v2/_catalog
|
|
```
|
|
|
|
]
|