From ee07a7dcbe5c92da3a70dc626d0f2e159ced97d4 Mon Sep 17 00:00:00 2001
From: shamoon <4887959+shamoon@users.noreply.github.com>
Date: Thu, 22 May 2025 09:45:18 -0700
Subject: [PATCH] Fix: remove non-working pathPrefix option for docker
 connections

---
 docs/configs/docker.md     | 5 ++---
 src/utils/config/docker.js | 4 ----
 2 files changed, 2 insertions(+), 7 deletions(-)

diff --git a/docs/configs/docker.md b/docs/configs/docker.md
index af3eabb64..8f1c10b30 100644
--- a/docs/configs/docker.md
+++ b/docs/configs/docker.md
@@ -79,16 +79,15 @@ my-docker:
 
     Note: This does not require TLS certificates if the proxy handles encryption. Do not use `protocol: https` unless you’re sure the target host supports HTTPS.
 
-You can further customize the connection options via `pathPrefix` and `headers`:
+You can also include `headers` for the connection, for example, if you are using a reverse proxy that requires authentication:
 
 ```yaml
 my-docker:
   host: dockerproxy
   port: 443
   protocol: https
-  pathPrefix: /docker_api/ # If a reverse proxy serves the API on a subpath
   headers:
-    Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ== # Send an authorization header if the API access is secured via basic auth
+    Authorization: Basic <base64-encoded-credentials>
 ```
 
 ## Using Socket Directly
diff --git a/src/utils/config/docker.js b/src/utils/config/docker.js
index 1fa3f3edf..4e2277f5d 100644
--- a/src/utils/config/docker.js
+++ b/src/utils/config/docker.js
@@ -47,10 +47,6 @@ export default function getDockerArguments(server) {
         res.conn.protocol = servers[server].protocol;
       }
 
-      if (servers[server].pathPrefix) {
-        res.conn.pathPrefix = servers[server].pathPrefix;
-      }
-
       if (servers[server].headers) {
         res.conn.headers = servers[server].headers;
       }