Enhancement: support specifying protocol for Docker Socket Proxy (#5285)
Docker CI / Linting Checks (push) Has been cancelled
Docker CI / Docker Build & Push (push) Has been cancelled

Co-authored-by: shamoon <4887959+shamoon@users.noreply.github.com>
This commit is contained in:
Marcin Grabda
2025-05-18 07:02:35 -07:00
committed by GitHub
co-authored by shamoon
parent 81547f8806
commit 3f160cc4ae
2 changed files with 17 additions and 0 deletions
+13
View File
@@ -66,6 +66,19 @@ my-docker:
port: 2375
```
Use `protocol: https` if you’re connecting through a reverse proxy (e.g., Traefik) that serves the Docker API over HTTPS:
```yaml
my-docker:
host: dockerproxy
port: 443
protocol: https
```
!!! note
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.
## 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.
+4
View File
@@ -43,6 +43,10 @@ export default function getDockerArguments(server) {
res.conn.protocol = "https";
}
if (servers[server].protocol) {
res.conn.protocol = servers[server].protocol;
}
return res;
}