From 07a8d42adfcb9b08fb27c98e0a1fb60bdde3dd70 Mon Sep 17 00:00:00 2001 From: inventivejon <50767589+inventivejon@users.noreply.github.com> Date: Thu, 20 Jun 2019 09:17:18 +0200 Subject: [PATCH] Update README.md --- README.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 89d8d1a..869cba6 100644 --- a/README.md +++ b/README.md @@ -1,9 +1,6 @@ # local_docker_swarm_registry Docker Registry for use in docker-swarm with nginx as proxy to only allow from server_name localhost and deny all other -Before you start: -Replace in docker-compose.yml file wit a username and with a password. You will not need it in operation. It is only for internal security. - You can use it by calling the script StartRegistry.sh >> sudo ./StartRegistry.sh @@ -14,6 +11,14 @@ You can stop it by calling StopRegistry.sh You can call and use the registry from all connected docker swarm nodes from the docker swarm you deployed to. ->> curl 127.0.0.1:5001/v2/_catalog +>> curl 127.0.0.1:5000/v2/_catalog and PLEASE don't use localhost instead. Will not work. + +Example for docker push: +>> docker push 127.0.0.1:5000/simpledreamer_sb_frontend + +If you find any issues please report. + +Known limitations: +- [swarmpit] Cannot manage registry from swarmpit since swarmpit would try to connect from other container with has its own localhost. Changing the swarmpit container to host network would solve but then the container would not be accessible any more by swarmpit webpage. If anyone has an idea how to solve feel free to contribute. For anyone who don't need managin the registry over swarmpit should be fine.