Enhancement: Support more docker API connection options. (#5304)

This commit is contained in:
Florian Apolloner 2025-05-22 16:35:29 +02:00 committed by GitHub
parent ea37ab2f78
commit 6cf3abd45e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 20 additions and 0 deletions

View File

@ -79,6 +79,18 @@ my-docker:
Note: This does not require TLS certificates if the proxy handles encryption. Do not use `protocol: https` unless youre sure the target host supports HTTPS. Note: This does not require TLS certificates if the proxy handles encryption. Do not use `protocol: https` unless youre sure the target host supports HTTPS.
You can further customize the connection options via `pathPrefix` and `headers`:
```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
```
## Using Socket Directly ## Using Socket Directly
If you'd rather use the socket directly, first make sure that you're passing the local socket into the Docker container. If you'd rather use the socket directly, first make sure that you're passing the local socket into the Docker container.

View File

@ -47,6 +47,14 @@ export default function getDockerArguments(server) {
res.conn.protocol = servers[server].protocol; 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;
}
return res; return res;
} }