Download Latest Version cri-dockerd-0.4.10.win.amd64.zip (16.7 MB) Google Add to Preferred Sources
Home / v0.4.8
Name Modified Size InfoDownloads / Week
Parent folder
cri-dockerd-0.4.8-3.el8.src.rpm 2026-10-08 16.8 MB
0
cri-dockerd-0.4.8-3.el8.x86_64.rpm 2026-10-08 12.4 MB
0
cri-dockerd-0.4.8-3.el9.src.rpm 2026-10-08 16.8 MB
0
cri-dockerd-0.4.8-3.el9.x86_64.rpm 2026-10-08 12.3 MB
0
cri-dockerd-0.4.8-3.fc40.src.rpm 2026-10-08 16.8 MB
0
cri-dockerd-0.4.8-3.fc40.x86_64.rpm 2026-10-08 12.2 MB
0
cri-dockerd-0.4.8-3.fc41.src.rpm 2026-10-08 16.8 MB
0
cri-dockerd-0.4.8-3.fc41.x86_64.rpm 2026-10-08 12.2 MB
0
cri-dockerd-0.4.8.amd64.tgz 2026-10-08 16.4 MB
0
cri-dockerd-0.4.8.arm64.tgz 2026-10-08 14.4 MB
0
cri-dockerd-0.4.8.darwin.amd64.tgz 2026-10-08 16.3 MB
0
cri-dockerd-0.4.8.darwin.arm64.tgz 2026-10-08 14.7 MB
0
cri-dockerd-0.4.8.win.amd64.zip 2026-10-08 16.6 MB
0
README.md 2026-10-08 851 Bytes
0
v0.4.8 source code.tar.gz 2026-10-08 16.5 MB
0
v0.4.8 source code.zip 2026-10-08 22.4 MB
0
Totals: 16 Items   233.6 MB 0

Fixes [#569]: streaming exec and attach fail against Kubernetes 1.36 and newer.

The streaming server was configured with a scheme-relative BaseURL ("/cri/"), so exec and attach URLs were advertised without a scheme or host. Kubernetes 1.36 enables ExtendWebSocketsToKubelet by default, which connects directly to the advertised URL rather than tunneling through the API server. The client then resolves the relative URL against the originating request's scheme (HTTPS) while the streaming server listens plaintext, producing:

http: server gave HTTP response to HTTPS client

Leaving BaseURL nil lets streaming.NewServer populate the correct scheme and host.

Note that --streaming-bind-addr is not a workaround: it corrects the advertised host but not the missing scheme.

Verified against Kubernetes 1.37.1 with the WebSocket exec path enabled.

Source: README.md, updated 2026-10-08