Soften the Docker troubleshooting note.
Signed-off-by: Jason Volk <jason@zemos.net>
This commit is contained in:
@@ -1,17 +1,11 @@
|
|||||||
# Troubleshooting Tuwunel
|
# Troubleshooting Tuwunel
|
||||||
|
|
||||||
> ## Docker users ⚠️
|
> [!IMPORTANT]
|
||||||
>
|
|
||||||
> Docker is extremely UX unfriendly. Because of this, a ton of issues or support
|
|
||||||
> is actually Docker support, not tuwunel support. We also cannot document the
|
|
||||||
> ever-growing list of Docker issues here.
|
|
||||||
>
|
|
||||||
> If you intend on asking for support and you are using Docker, **PLEASE**
|
> If you intend on asking for support and you are using Docker, **PLEASE**
|
||||||
> triple validate your issues are **NOT** because you have a misconfiguration in
|
> triple validate your issues are **NOT** because you have a misconfiguration in
|
||||||
> your Docker setup.
|
> your Docker setup. We must remain focused on supporting Tuwunel issues and
|
||||||
>
|
> cannot budget our time for generic Docker support. Compose file issues or
|
||||||
> If there are things like Compose file issues or Dockerhub image issues, those
|
> Dockerhub image issues are okay if they are something we can fix.
|
||||||
> can still be mentioned as long as they're something we can fix.
|
|
||||||
|
|
||||||
## Tuwunel and Matrix issues
|
## Tuwunel and Matrix issues
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user