* more copyedits
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* copyedit
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* copyedits and wording changes per reviews
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* add back in explanation of Dockerfile commands
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* Update part2.md
* Add notes
After Docker Cloud Agent installed successfully, and run the `docker swarm init` and `docker swarm join` commands will got the errors, and can not register swarm with Docker Cloud.
```
*******************************************************************************
Docker Cloud Agent installed successfully
*******************************************************************************
You can now deploy containers to this node using Docker Cloud
ubuntu@test:~$ docker swarm init
docker: 'swarm' is not a docker command.
See 'docker --help'.
ubuntu@test:~$ sudo docker run -ti --rm -v /var/run/docker.sock:/var/run/docker.sock dockercloud/registration
Unable to find image 'dockercloud/registration:latest' locally
latest: Pulling from dockercloud/registration
79650cf9cc01: Pull complete
e720390eb80b: Pull complete
7b619be6318c: Pull complete
Digest: sha256:b0c89c6a446700394c7b85d93b9b1117e517504c64577586f535ceec353628e7
Status: Downloaded newer image for dockercloud/registration:latest
Error response from daemon: 404 page not found
```
So, `Use the Docker Cloud Agent to Bring your Own Host` does not support swarm mode.
* formatted note, clarified Cloud standard and swarm modes
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* copyedits, rewrites
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* copyedits
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* streamlined get start prereqs
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* copyedit for line spacing
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* getting started edits, improvements to flow
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added image of app in browser, more subtopics
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* copyedit of Orientation
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* copyedits, rewording, examples, additions for swarms and services
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* review comments, troubleshooting hints and clarifications
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* corrected cloud link to AWS beta swarm topic, added Azure
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
Following the steps above I spent several hours trying to "Troubleshoot slow Docker swarm performance" as each web server in my stack was taking 'forever' to respond to HTTP requests, but worked just fine when invoked directly. I noticed it was taking almost exactly 30 seconds every time, and when finishing the turorial (thus deploying Redis) I realized that the python apps were waiting for some kind of Redis timeout. After deploying with a working Redis service responses were quick as before.
As somebody new to Docker it would have been good to know that the web app itself (timing out for Redis) was causing the delay not the host system or docker configuration.
This change will make sure request gets completed quickly. Without these it takes more than a minute for request to finish. This is especially important for beginners because they might not understand why request is taking so much time. Adding these parameters request completes quickly.
aiueogawa
Gwendolynne Barr
French Ben
Misty Stanley-Jones
nemophila
Victoria Bialas
Wang Jie
David Muganza
Jochen
Tim Sorbera
Taio Jia
Kamlesh
Andres Salgado
Dave
joeabbey
Ed Solis
Chris Schooley
Aaron Shaver
Alex Pulver
Rahiel Kasim
Shekhar Gulati
Michel Ruffieux
Dara Kong
Gabriel Baims
Martin Folkers
Shlomi Izikovich
John Mulhausen
Steven Hanna
Bill
marvin sl