From 5d5e551104a5a2c759cf3ded29a49fb05631f2d9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ant=C3=B3nio=20Alvarenga?= Date: Fri, 7 May 2021 11:26:18 +0100 Subject: [PATCH] Multi-container apps: add workaround for non amd64 machines --- docs/tutorial/multi-container-apps/index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/tutorial/multi-container-apps/index.md b/docs/tutorial/multi-container-apps/index.md index 68a0ed0..3781ef1 100644 --- a/docs/tutorial/multi-container-apps/index.md +++ b/docs/tutorial/multi-container-apps/index.md @@ -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 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. + + !!! 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.