From bdaedc2f7e452386b4b2e3211ffdcbdbccafccd3 Mon Sep 17 00:00:00 2001 From: Anton Livaja Date: Thu, 19 Dec 2024 15:04:47 -0500 Subject: [PATCH] fix instructions to use docker create --- quorum-key-management/src/sdtool-instructions.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/quorum-key-management/src/sdtool-instructions.md b/quorum-key-management/src/sdtool-instructions.md index d938286..4e1bd60 100644 --- a/quorum-key-management/src/sdtool-instructions.md +++ b/quorum-key-management/src/sdtool-instructions.md @@ -12,9 +12,7 @@ This tool is also available via [stagex](https://registry.hub.docker.com/r/stage * `docker pull stagex/sdtool` 1. Extracting binary: - * Run docker container: `docker run -p 4000:80 --name sdtool stagex/sdtool` - * This will error out the first time, run the command again and then you will get an error that's different that looks like this: `docker: Error response from daemon: Conflict. The container name "/sdtool" is already in use by container "679a52775dfce91f66d8894925449242eacbf4b0aeccaf2effe2c5e213e60a6b". You have to remove (or rename) that container to be able to reuse that name.`. Copy the container ID from the error message and use it in the next command - * This issue occurs because of bin/sh missing in the image so we can't run the container properly + * Run docker container: `docker create -p 4000:80 --name sdtool stagex/sdtool` * Copy image to tar: `docker export -o sdtool.tar` * Extract binary from tar: `mkdir -p sdtool-dir | tar -xvf sdtool.tar -C sdtool-dir | cp sdtool-dir/usr/bin/sdtool ./sdtool` * You can verify the container hash: