In docker-compose.dev.yml, DATABASE_CONNECTIONSTRING is used as a database URL whereas, in the code, CONNECTIONSTRING is being used. Hence, updating the string in docker-compose.dev.yml file.
The page in the Docker Hub section is a better match for the old content:
https://github.com/docker/docker.github.io/blob/v1.12-release/engine/tutorials/dockerrepos.md)
And fits better with the description around the link in the CLI reference;
> The image can be any valid image – it is especially easy to start by pulling
> an image from the Public Repositories.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
It didn't use the volumes as parameter, instead it defined a service called volumes and services don't have a parameter called mongodb. Corrected indentation in yml file
See https://web.dev/external-anchors-use-rel-noopener/
Using noopener, as that addresses the security issue. "noreferer" blocks
the REFERER header, which may still be useful for some target URLs.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
- Updated the Guides tab to open to the Get started page, instead of Develop with Docker.
- Moved Docker overview as the first entry in the Guides toc.
* Adding in Cloud steps to tutorial
Adding in bullet points referencing how to get started with the cloud in the tutorial and linking to current best blog posts
* Update part2.md
`--force` in `rm --force` claimed to remove the container (which `rm` obviously does). `--force` allows a container to be removed even if it's still running.
- Move getting started overview to /get-started/overview/
- Move engine installation files under /engine/
- Redirect the top-level /install/ to /get-docker/
- Updated titles in left-hand navigation
- Added back some pages to the navigation that were
currently not included.
- Reduce some steps in the installation pages
- Move devicemapper prerequisites to the devicemapper
storage driver page.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
The long forms of Docker commands have not caught on. I don't think we
should continue to encourage their use especially in the get started
guide. There is no evidence from online searches that anyone is really
using them. They are overly pedantic and verbose.
Signed-off-by: Justin Cormack <justin.cormack@docker.com>
* Update Get started docs
* update part-1, add redirects
* draft updates to part 2 and 3
* tidy up the orchestration topics
* update examples, and other minor edits
* address Stefan's review comments
* moved orchestration to a new node
* fix Ben's review comments
* add email verification step
* Emphasize the CTA in part 3
* first pass at gs pt 1
* suggestions from Dawn
* unbreak tabs
* get started part 2 refresh
* comments from Dawn and Adrian
* draft of kube get started
* first draft of swarm demo for gs
* saving some updates...
* first draft docker hub section
* comments from Dawn
* comments from Dawn
* comments from Dawn
* comments from Dawn
* gsu frontmatter
* removed toc entry for get started part 6 and changed toc titles for the rest of get started topics
* addressing Adrian's feedback
* fixing top nav buttons
* Fixed typo and added port number
Lost couple minutes figuring out on which port is app running on vm-s. So I think it would be nice to add port number in description or change picture a little.
* Update part4.md
standardizing formatting
Changed from old outdated Edge release to reflect use of a stable release. Kubernetes page actually reflects this version as well (so its an error on this page only).
Part 4 doesn't include instructions to change the port forwarding to 80:80 in this section. The screenshot is a bit misleading if you're coming directly from part 3 and have port 4000 still forwarding to port 80.
When you use `docker service ls`, it won't show you the list of services. Instead use `docker stack services getstartedlab` to show the service that was created and thereby getting the Service ID of it.
As this is an introductory document, using short options
and relying on default behaviors without explanation
may cause some confusion.
This change it explicit how the --tag option is being used.
It also uses an equal sign to visually group the option and its value,
so that the . at the end of the command doesn't go unnoticed.
Fixed a typographical error on line 246 - " we just map port 80 on the host to port 80 in the container" should be " we just map port 4000 on the host to port 80 in the container"
In the docker-compose file, the ports sections maps host port 4000 to container port 80, so if we want to see our app in a browser we should check on port 4000.
Proxy settings titles was placed in the DNS misconfiguration part, and the DNS settings title was placed in the proxy configuration part. This changes moves the places of the titles so that they both present the section they intend to.
The host port was set to 80, which was both inconsistent with the previous tutorial and also causing issues when following the tutorial on Windows.
For reference, here is the error when attempting to run a container on port 80:
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: driver failed programming external connectivity on endpoint focused_euler (079893ea98df78bf7043f86072263317be106cbb7f4a3fcde23c2ef19ad39a01): Error starting userland proxy: Bind for 0.0.0.0:80: unexpected error Permission denied.
ERRO[0000] error waiting for container: context canceled
* Add a note for the DNS settings
Reason: a lot of people struggle against problems with the DNS configuration when they try to build their first app.
* Merge DNS and proxy notes
* Reword lots of instances of 'will'
* Reword lots of instances of won't
* Reword lots of instances of we'll
* Eradicate you'll
* Eradicate 'be able to' type of phrases
* Eradicate 'unable to' type of phrases
* Eradicate 'has / have to' type of phrases
* Eradicate 'note that' type of phrases
* Eradicate 'in order to' type of phrases
* Redirect to official Chef and Puppet docs
* Eradicate gratuitous 'please'
* Reduce use of e.g.
* Reduce use of i.e.
* Reduce use of N.B.
* Get rid of 'sexagesimal' and correct some errors
* rough pass at tabs, jsonification
* GHPages 147, authoring YML, sitemap via plugin, working JS
* Update Gemfile
* Removing dk.rb artifact
* Simplifying authoring YML even more
* More YML simplification
* Remove jekyll-seo -- even more perf gain
* Glossary support
* Collections support
* Incremental off; GH Pages 172 gets build time to 50 seconds
* Added reference to proxy settings
Added reference to proxy settings in part 2 since proxy needs to be configured in order to run hello-world container.
* Update index.md
add newline
* Update index.md
fixed link
I had certificates issues when the pip command was run:
There was a problem confirming the ssl certificate: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)
Using the pip like this solved the issue:
RUN pip install --trusted-host pypi.python.org -r requirements.txt
* images to cover AWS deploy
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added instructions on opening ports with security groups in AWS
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* finalized cloud deploy procedure, added info re: unset docker-machine variables
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added screen snaps, cleanup, and iteration steps to cloud example
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* removed edge releases qualification on swarm connect from Desktop apps
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added visualizer on cloud screen snap
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* moved iteration, cleanup step to be without CE steps in part 6
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* Provide advice about adding to the docker group
You need to add a standard user to the docker group to prevent sudo when calling docker
* Added link to post-install instructions
* added note re: setting ENV variables for proxy servers in Dockerfile
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* review comments
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* reworded note title, removed link out to ENV per review comments
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added info to docs test page about how to link to auto-generated reference pages
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added more info to test on re: linking
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* format ENV as a command
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* clarified rebuild and publish as part of iterating on app
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* copyedits
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* stop gap measure to fix data persistence part of the tutorial
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* improved note about data directory and scp
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* how to get scp to work on Windows
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* clarified some commands in part 3
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* fixed links on hyperv, machine pages
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* removing notes about scp and ssh on Windows, WIP
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* WIP: adding docker-machine env commands
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added docker-machine env option, re-worked tabs
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* moved extra info re: docker-machine env out of note, to end of part 4
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* updated parts 4, 5 with docker-machine env, added note re: commands
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* changed rest of ssh examples, formatting fixes, copyedit
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* copyedit on docker-machine env example
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* reworded note title
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* 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.