From 80089aed10c15a597a16824e24d46991001fc29c Mon Sep 17 00:00:00 2001 From: Sachin Agarwal Date: Mon, 21 Nov 2022 14:45:23 -0500 Subject: [PATCH] Added rm flag to remove stopped docker container, also removed roboflow executable as its already inclded in the entrypoint so shouldn't be added to the docker run --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1f6f65c..d3c9c49 100644 --- a/README.md +++ b/README.md @@ -70,11 +70,11 @@ Then, run the roboflow cli docker image interactively like so ``` # Authorize -docker run -it -v ~/.config/roboflow:/root/.config/roboflow roboflowcli:latest auth +docker run -it --rm -v ~/.config/roboflow:/root/.config/roboflow roboflowcli:latest auth # Use the CLI as usual inside a docker container. -docker run -it -v ~/.config/roboflow:/root/.config/roboflow roboflowcli:latest project list +docker run -it --rm -v ~/.config/roboflow:/root/.config/roboflow roboflowcli:latest project list ``` Here we have mounted the roboflow credentials into the docker container. The first docker command authorizes the user and stores credentials