Stop gap measure to fix data persistence part of the tutorial #4725
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.
What's changed
Added back in
docker-machine scp
anddocker-machine ssh
commands in part 5 to get the the data persistence step with theredis
service to work. With the current Compose file, when you run thedocker stack deploy
command on the local host withmyvm1
active, Docker looks for the~./data
directory on the local host, not on the remote machine,myvm1
.Added an override to the
redis
command in the Compose file to get the data to persist.Related
Addresses #4723, but we will leave the issue open to further research getting this to work without
scp
if possible.Related PR is #4675
Reviewers
@shin- @friism @johndmulhausen @jasonmevans @mstanleyjones
Signed-off-by: Victoria Bialas victoria.bialas@docker.com