adelorenzo/getting-started
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Multi-container apps: add workaround for non amd64 machines

Browse Source
This commit is contained in:
António Alvarenga 2021-05-07 11:26:18 +01:00 committed by GitHub
parent 13386236e4
commit 5d5e551104
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/tutorial/multi-container-apps/index.md
View File

@ -66,6 +66,11 @@ For now, we will create the network first and attach the MySQL container at star
You'll notice we're using a volume named `todo-mysql-data` here and mounting it at `/var/lib/mysql`, which is You'll notice we're using a volume named `todo-mysql-data` here and mounting it at `/var/lib/mysql`, which is
where MySQL stores its data. However, we never ran a `docker volume create` command. Docker recognizes we want where MySQL stores its data. However, we never ran a `docker volume create` command. Docker recognizes we want
to use a named volume and creates one automatically for us. to use a named volume and creates one automatically for us.
!!! info "Troubleshooting"
If you see a `docker: no matching manifest` error, it's because you're trying to run the container in a different
architecture than amd64, which is the only supported architecture for the mysql image at the moment. To solve this
add the flag --platform linux/amd64 in the previous command
1. To confirm we have the database up and running, connect to the database and verify it connects. 1. To confirm we have the database up and running, connect to the database and verify it connects.