* Update 07_multi_container.md
Add a script that works on M1 chips for people following this guide on Apple Silicon.
* Add shell prompt, use linux/amd64
Co-authored-by: Stefan Scherer <stefan.scherer@docker.com>
The "docker build" example was written as an in-line example, but directly
followed by a full-stop at the end of the sentence, which made it easy to
confuse the extra `.` to be part of the command to run.
This moves it to a code block to allow the example to be highlighted, and
less confusing.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
In THE DOCKER PLATFORMsection , there is a small grammaratical error in second line it should be "The isolation and security allows you to run many
containers simultaneously on a given host." (allow->allows) not "The isolation and security allow you to run many
containers simultaneously on a given host."
* edit: updated `Security scanning` section
`docker scan` fails when user is not logged in to Docker Hub. First I had to use `docker login` to login to Docker Hub. Afterwards, `docker scan` worked.
* Update 09_image_best.md
Update format, fix a typo
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
The current documentation references the newer todo list built in the [Getting Started demo](https://docs.docker.com/get-started/02_our_app/) built in previous steps, but the docs listed the code for the older [BulletinBoard:1.0 image](http://www.myclass5.cn/get-started/part2/). So, this patch applies the following to run Getting Started:
- changed the name of the image to `getting-started`, and rebuild the image using `docker build -t getting-started .`
- changed the port numbers under the `ports` key in the Kubernetes YAML to *3000*
The created docker network `todo-app` was unable to support an authentication protocol requested by MySQL versions 8.0 and higher. I included a fix suggested by **stackoverlfow** user [Pras](https://stackoverflow.com/a/50131831/11492382).
* Updated `## Persist the todo data` section
I provided a 3-step procedure from lines 81 to 102 on how to access the container's shell environment, since It was unclear how to access the `/etc/todos` directory. Also, nowhere, in the tutorial, was it mentioned that containers are *self-contained shell environments*. This information is crucial for beginners following along with the tutorial.
Take care.
* Second update
This update was due to a suggestion provided by @thaJeztah .