From c7696d344a70afc29f8fdfb9cfa2698fb1cbfca4 Mon Sep 17 00:00:00 2001 From: decentral1se Date: Fri, 4 Feb 2022 13:49:20 +0100 Subject: [PATCH] refer to add once more --- docs/abra/trouble.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/abra/trouble.md b/docs/abra/trouble.md index 4656e01c..8da5786b 100644 --- a/docs/abra/trouble.md +++ b/docs/abra/trouble.md @@ -52,7 +52,7 @@ Due to a limitation in our implementation, `abra` uses 2 methods of making SSH c ## "abra server ls" shows the wrong details? -You can use `abra server rm` to remove the incorrect details. Make sure to take a backup of your `~/.abra/servers/` first. +You can use `abra server rm` to remove the incorrect details. Make sure to take a backup of your `~/.abra/servers/` first. You can then try to re-create by using `abra server add ...` again, making sure to take care if you need to use ` `, see `abra server add -h` for more help on this. However, if you have Docker installed on the same machine you have `abra`, then there might be some confusion. If you run `docker context ls` you'll see that Docker uses context connection strings also. `abra` simply uses this approach. Sometimes, your Docker defined context details & your `abra` context details can get out of sync. You can use `docker context rm` to resolve this.