- To reduce the error prone process of grabbing all Python packages in the global Python scope, the specific package is extracted and set in to the requirements.txt file
BuildKit allows using alternative Dockerfile syntaxes to introduce new features
without having to update Docker itself. The general recommendation is to always
specify a "syntax" directive in a Dockerfile, so that (if needed) older versions
of Docker can download the correct syntax to build the Dockerfile.
This updates our examples to include a syntax directive, to make users more familiar
with these directives, and to illustrate best-pracitces in our documentation.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Quick grammar fix: run -> runs
Set the mysql server to use the root password as used in the Flask application
Changed checking the MySQL server from using `docker run` to `docker exec` since you want to log in to the existing mysql container. Added the password as set by the previous `docker run` command.
Changed @app.route to `initdb`, the path used in later parts of the tutorial.
(cherry picked from commit 473930c972)
Replaced `docker-python` directory reference with `python-docker` to reduce confusion when following the tutorial. The tutorial establishes creating a `python-docker` directory, so proposing this change to maintain consistency with instructions.
* Fix CMD arguments
The previous CMD command doesn't actually start the service.
* Simplify (and fix) curl command
Previously it was specifying a lot of parameters that in our case are optional and IMO don't help with understanding what's going on.
Furthermore the previous command was asking for a `/test` page which we do not serve.
And finally it was using POST which is not supported in our app created in the previous step.
* Fix typo