Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop gap measure to fix data persistence part of the tutorial #4725

Merged
merged 2 commits into from
Sep 27, 2017
Merged

Stop gap measure to fix data persistence part of the tutorial #4725

merged 2 commits into from
Sep 27, 2017

Conversation

londoncalling
Copy link
Contributor

@londoncalling londoncalling commented Sep 27, 2017

What's changed

  • Added back in docker-machine scp and docker-machine ssh commands in part 5 to get the the data persistence step with the redis service to work. With the current Compose file, when you run the docker stack deploy command on the local host with myvm1 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

Victoria Bialas added 2 commits September 26, 2017 18:01
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
@londoncalling londoncalling merged commit 410ed46 into docker:master Sep 27, 2017
@@ -85,7 +85,7 @@ with the following. Be sure to replace `username/repo:tag` with your image detai
visualizer:
image: dockersamples/visualizer:stable
ports:
- "8080:8080"
- "8080:8080":
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this colon intentional?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't speak for whether it is intentional but I can confirm that it doesn't actually break YAML.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's not intentional, I believe. I'll remove it. Working with @shin- on this problem today.

@londoncalling londoncalling mentioned this pull request Sep 27, 2017
@londoncalling londoncalling deleted the get-started-redis-errors branch September 28, 2017 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants