Docker service registry not running correctly (Replicas 0/1)#4641
Merged
mdlinville merged 3 commits intodocker:masterfrom Sep 19, 2017
Merged
Docker service registry not running correctly (Replicas 0/1)#4641mdlinville merged 3 commits intodocker:masterfrom
mdlinville merged 3 commits intodocker:masterfrom
Conversation
As it is said in the text before "The example bind-mounts `/mnt/registry` on the swarm node to `/var/lib/registry/` within the container." the example uses a bind-mount instead of a volume-mount (see difference here in the docs: https://docs.docker.com/engine/swarm/services/#give-a-service-access-to-volumes-or-bind-mounts). As bind-mounts are only applied with `type=bind` configuration parameter of `--mount`, it has to be added here so that the `swarm-registry` service is able to start. Additionally, the bind-mount relies on the pre-existing src-directory `/mnt/registry`, which should also be added to the documentation - see important notes "If you bind mount a host path into your service’s containers, the path must exist on every swarm node." in https://docs.docker.com/engine/swarm/services/#give-a-service-access-to-volumes-or-bind-mounts.
jonashackt
added a commit
to jonashackt/ansible-windows-docker-springboot
that referenced
this pull request
Sep 15, 2017
…/1)"-error, see docker/docs#4641 We need to configure the bind-mount in the --mount configuration parameters of docker service create command, as the docs state. Also added constraint to only replicate registry on Linux nodes and created `/mtn/registry` directory on all Linux nodes.
mdlinville
suggested changes
Sep 15, 2017
mdlinville
left a comment
There was a problem hiding this comment.
Please resolve the conflict. Also, please don't abbreviate source as src when you're not talking about specific directory called src.
Contributor
Author
|
Resolved the conflict and changed |
mdlinville
approved these changes
Sep 19, 2017
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As it is said in the text before "The example bind-mounts
/mnt/registryon the swarm node to/var/lib/registry/within the container." the example uses a bind-mount instead of a volume-mount (see difference here in the docs: https://docs.docker.com/engine/swarm/services/#give-a-service-access-to-volumes-or-bind-mounts). As bind-mounts are only applied withtype=bindconfiguration parameter of--mount, it has to be added here so that theswarm-registryservice is able to start.Additionally, the bind-mount relies on the pre-existing src-directory
/mnt/registry, which should also be added to the documentation - see important notes "If you bind mount a host path into your service’s containers, the path must exist on every swarm node." in https://docs.docker.com/engine/swarm/services/#give-a-service-access-to-volumes-or-bind-mounts.Proposed changes
Updated the docs.
Related issues (optional)
moby/moby#25912
moby/moby#34532