From 3c5bd986afdd23a22d47da671441e4a3deec204d Mon Sep 17 00:00:00 2001 From: kenny Date: Wed, 13 Mar 2024 16:53:17 +0000 Subject: [PATCH] GITBOOK-45: Add note about platform --- nakamoto-upgrade/running-a-signer.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/nakamoto-upgrade/running-a-signer.md b/nakamoto-upgrade/running-a-signer.md index c532d6af12..9a03242cac 100644 --- a/nakamoto-upgrade/running-a-signer.md +++ b/nakamoto-upgrade/running-a-signer.md @@ -53,9 +53,7 @@ You can run the signer as a Docker container using the `blockstack/stacks-core` * You’ll need a volume with at least a few GB of available storage that contains the folder your `db_path` is in. In the above example, that would be /var * You’ll need to include your `signer-config.toml` file -An example command for running the Docker image with ”`docker run`”: - -Be sure to remove the comments before running, these are just for illustrative purposes. +An example command for running the Docker image with ”`docker run`” (be sure to remove the comments before running): ```bash docker run -d \ @@ -68,6 +66,12 @@ docker run -d \ --reward-cycle 1 ``` +{% hint style="info" %} +If you get an error saying that the manifest cannot be found, you are probably running on system architeecture other than x64 arch. Since you are using a PR release (`next`) you'll need to specify your platform with the `--platform` flag. + +For example, if you are running on M1 Mac, you would add `--platform=limux/amd64` to the below command. +{% endhint %} + Or, with a custom Dockerfile: ```docker