Portainer problem in windows docker 4.52.0

Docker Desktop
1

here i m facing the problems
portainer could not open the local docker /var/run/docker.sock in windows docker 4.52.0
it s working fine on version 4.51.0
even using default config

docker run -d `
  -p 8000:8000 `
  -p 9000:9000 `
  --name=portainer `
  --restart=always `
  -v /var/run/docker.sock:/var/run/docker.sock `
  -v portainer-data:/data `
  -v /:/host `
  portainer/portainer-ce

a another problem No More /etc/fstab setup? - Docker Desktop - Docker Community Forums
the setup is create a network driver in windows as Z:
add Z: /mnt/host/z drvfs nofail 0 0 to \etc\fstab and mkdir -p ./mnt/host/z
after version 4.43.2 all the setup in wsl -d docker-desktop wont be saved 
 now need edit wsl/resource/ext4.vhx or wsl-bootstrap.tar to make the etc changing happen


2

I tried to verify the issue on 4.52.0.

PS C:\Users\metin> docker version
Client:
 Version:           29.0.1
 API version:       1.52
 Go version:        go1.25.4
 Git commit:        eedd969
 Built:             Fri Nov 14 16:19:55 2025
 OS/Arch:           windows/amd64
 Context:           desktop-linux

Server: Docker Desktop 4.52.0 (210994)
 Engine:
  Version:          29.0.1
  API version:      1.52 (minimum version 1.44)
  Go version:       go1.25.4
  Git commit:       198b5e3
  Built:            Fri Nov 14 16:17:57 2025
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          v2.1.5
  GitCommit:        fcd43222d6b07379a4be9786bda52438f0dd16a1
 runc:
  Version:          1.3.3
  GitCommit:        v1.3.3-0-gd842d771
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

PS C:\Users\metin> docker run -d `
>>   -p 8000:8000 `
>>   -p 9000:9000 `
>>   --name=portainer `
>>   --restart=always `
>>   -v /var/run/docker.sock:/var/run/docker.sock `
>>   -v portainer-data:/data `
>>   -v /:/host `
>>   portainer/portainer-ce
Unable to find image 'portainer/portainer-ce:latest' locally
latest: Pulling from portainer/portainer-ce
4f4fb700ef54: Pull complete
04f56cab0724: Pull complete
6109bb7d1248: Pull complete
e80185cdbc79: Pull complete
666c509ccde9: Pull complete
da18f9659f11: Pull complete
a48e87497a08: Pull complete
7e764748a0e3: Pull complete
Digest: sha256:83fab9ec8e05a9ca17c64d2288fef25f498124eccdbcd12eaff9238870884630
Status: Downloaded newer image for portainer/portainer-ce:latest
6d4274b522883ad847e796c5c6e85a502ec3175128ef1c5b5dc7eef50506b0d2

PS C:\Users\metin> docker ps -a
CONTAINER ID   IMAGE                                      COMMAND                  CREATED         STATUS          PORTS                                                                                      NAMES
6d4274b52288   portainer/portainer-ce                     "/portainer"             4 seconds ago   Up 6 seconds    0.0.0.0:8000->8000/tcp, [::]:8000->8000/tcp, 0.0.0.0:9000->9000/tcp, [::]:9000->9000/tcp   portainer
41aa6af783dc   dockersamples/labspace-interface:v0.15.0   "docker-entrypoint.s
"   2 weeks ago     Up 27 seconds   0.0.0.0:3030->3030/tcp, [::]:3030->3030/tcp                                                labspace-interface-1

I can see the embedded Docker Engine from Docker Desktop in Portainer.

3

I tried too and it dosn’t work for me either. docker inspect portainer shows that /run/host-services/docker.proxy.sock was mounted from the virtual machine, not /var/run/docker.sock, which also exists.

It looks like a bug to me, because the Portainer extension doesn’t work either..

No, it is not a bug. Using the right client like this works:

docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock  docker:29-cli sh

But portainer still doesn’t support the new Docker version that came with the new Docker Desktop.

4

So apparently seeing this was not enough:

image
image2201×316 39.4 KB

I should have clicked the endpoint.

The problem is not the docker.sock. The problem is that portainer does not support the min API version v1.44 docker v29 requires.

If you configure the min API version to 1.24, portainer will work again:

  • open Docker Desktop settings → Docker Engine
  • add property min-api-version": "1.24"
  • click “Apply & restart” to restart the Docker Engine

Now Portainer will work again.

The resulting daemon configuration could look something like this:

{
  "builder": {
    "gc": {
      "defaultKeepStorage": "20GB",
      "enabled": true
    }
  },
  "experimental": true,
  "min-api-version": "1.24"
}
1 Like
Ubuntu 24.04 - Kasm - Docker Issues
TestContainer stopped working after updating Docker Desktop to v4.56.0
Macos gitlab-runner fails to run containers with version 4.52
5

Interestingly I have had problems with testcontainers (with testcontainers 2.0.2) as well, once I down graded the min-api-version it seems to be working as well.

6

great thanks~~~ wiil try soon

7

thats good news will wait for portainer update and set api version 1st

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.