p4u1/docs.coopcloud.tech
0
0
Fork 0
forked from toolshed/docs.coopcloud.tech
Code Pull Requests Activity

some more entries

Browse Source
This commit is contained in:
decentral1se
2022-02-03 14:37:34 +01:00
parent 4b212f1a05
commit e6810cfba9
1 changed files with 14 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/abra/trouble.md
View File

@ -4,9 +4,11 @@ title: Troubleshoot
## Where do I report `abra` bugs / feature requests? ## Where do I report `abra` bugs / feature requests?
You can use [this issue tracker](https://git.coopcloud.tech/coop-cloud/abra/issues/new).
## I'm having a bad day, where do I find a human? ## I'm having a bad day, where do I find a human?
TODO. Please see [the contact page](/intro/contact).
## SSH connection issues? ## SSH connection issues?
@ -14,7 +16,17 @@ TODO.
## "abra server ls" shows the wrong details? ## "abra server ls" shows the wrong details?
TODO. You can use `abra server rm` to remove the incorrect details. Make sure to take a backup of your `~/.abra/servers/<domain>` first.
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.
If you need to create a new context from Docker, you can do:
```
docker context create <domain> --docker "host=ssh://<user>@<domain>:<port>"
```
(This is what we used to before we wrote `abra` to make it more convenient.)
## Command-line flag handling is weird? ## Command-line flag handling is weird?