[Bug]: problem following documentation for Update tool in Neurodesk (codespaces)

[m9h]

Version

latest

What platform are you seeing the problem on?

Cloud

What happened

Following update tool documentation here https://neurodesk.org/developers/new_tools/update_tool/
Codespaces started but docker in docker was failing. Needed to make change to the base image
Changed "image": "mcr.microsoft.com/devcontainers/python:3.12-bookworm", adding -bookworm
Codespaces now successfully starts
Again following update tool documentation here https://neurodesk.org/developers/new_tools/update_tool/
./builder commands now have docker on PATH

"Docker image built successfully at fmriprep:25.2.3
Container tester image neurocontainers/container-tester:latest not found; building it now...
[+] Building 34.5s (11/11) FINISHED docker:default"

Now Error with " => => naming to docker.io/neurocontainers/container-tester:latest 0.0s
Error response from daemon: client version 1.52 is too new. Maximum supported API version is 1.43
RuntimeError: unable to create container from tester image: Command '['docker', 'create', 'neurocontainers/container-tester:latest']' returned non-zero exit status 1."

How to reproduce

No response

Relevant log output or screenshot

No response

[stebo85]

Dear @m9h - thank you for reporting that. That's a new feature @Vbitz added a few weeks ago and it doesn't seem to be supported on the github runner. @Vbitz - any idea what the issue could be?

[Vbitz]

How was docker in docker failing? As I recall it gives access to the VM docker socket running a privileged container.

That would explain the error from updating the docker version inside the container.

[stebo85]

@Vbitz - isn't the problem the new docker.io/neurocontainers/container-tester ?

[Vbitz]

The image is built locally rather than pushed. The error suggests a version mismatch in the Docker versions rather than an issue with the containers themselves.

[Vbitz]

The only reason it's built as a container is to save the user from setting up Golang on their system.

[stebo85]

correct - can you reproduce the problem?

[Vbitz]

Yes I can reproduce the issue. I fixed it but ran into another problem. Since codespaces run inside a docker container the docker commands need to be executed relative to the host environment not the codespaces. I'll work on a more robust solution when I get back next year.