Looking at the stats, the Windows docker version is running very well with ~90% of tasks returning successfully. For the failures, most seem to be of the form.

program: docker
read_from_pipe() error: timeout
get_container_state() failed: -182
2026-02-02 15:03:23 (12412): called boinc_finish(1)

I have seen on someones machine that it did this after returning successful tasks. If you have an issue like this please let us know as I would be interested to troubleshoot.

In reply to Laurence's message of 3 Feb 2026:

I have seen on someones machine that it did this after returning successful tasks. If you have an issue like this please let us know as I would be interested to troubleshoot.

Slightly different

creating container boinc__lhcathome.cern.ch_lhcathome__theory_2922-4848575-473_0
running docker command: images
program: podman
command output:
REPOSITORY                   TAG         IMAGE ID      CREATED        SIZE
docker.io/library/almalinux  9           df3270cc8bc8  10 months ago  217 MB
EOM
building image
running docker command: build "." -t boinc__lhcathome.cern.ch_lhcathome__theory_2922-4848575-473 -f Dockerfile 
program: podman
read_from_pipe() error: timeout
build_image() failed: -182

StdErr Output:

STEP 1/6: FROM almalinux:9
Resolved "almalinux" as an alias (/etc/containers/registries.conf.d/00-shortnames.conf)
Trying to pull docker.io/library/almalinux:9...
time="2026-02-05T12:51:34Z" level=warning msg="Failed, retrying in 2s ... (1/3). Error: initializing source docker://almalinux:9: pinging container registry registry-1.docker.io: Get \"https://registry-1.docker.io/v2/\": dial tcp 108.160.165.189:443: i/o timeout"
time="2026-02-05T12:52:06Z" level=warning msg="Failed, retrying in 2s ... (2/3). Error: initializing source docker://almalinux:9: pinging container registry registry-1.docker.io: Get \"https://registry-1.docker.io/v2/\": dial tcp 108.160.165.189:443: i/o timeout"
time="2026-02-05T12:52:38Z" level=warning msg="Failed, retrying in 2s ... (3/3). Error: initializing source docker://almalinux:9: pinging container registry registry-1.docker.io: Get \"https://registry-1.docker.io/v2/\": dial tcp 108.160.165.189:443: i/o timeout"
Error: creating build container: unable to copy from source docker://almalinux:9: initializing source docker://almalinux:9: pinging container registry registry-1.docker.io: Get "https://registry-1.docker.io/v2/": dial tcp 108.160.165.11:443: i/o timeout

running docker command: container rm boinc__lhcathome.cern.ch_lhcathome__theory_2922-4833264-489_0
program: podman
command output:
Error: no container with ID or name "boinc__lhcathome.cern.ch_lhcathome__theory_2922-4833264-489_0" found: no such container
EOM
running docker command: image rm boinc__lhcathome.cern.ch_lhcathome__theory_2922-4833264-489
program: podman
command output:
Error: boinc__lhcathome.cern.ch_lhcathome__theory_2922-4833264-489: image not known
EOM

BOINC Log:

2026/2/5 21:03:02 | LHC@home | Output file Theory_2922-4880029-490_0_r299485221_result for task Theory_2922-4880029-490_0 absent

I don't know why but I met nearly the same problem on BOINC Central before

In reply to Lezhe Gao's message of 5 Feb 2026:

BOINC Log:

2026/2/5 21:03:02 | LHC@home | Output file Theory_2922-4880029-490_0_r299485221_result for task Theory_2922-4880029-490_0 absent

I don't know why but I met nearly the same problem on BOINC Central before

The reason is in your log: i/o timeout

From your BOINC CENTRAL tasks:

Trying to pull docker.io/library/debian:latest...
time="2026-02-05T14:47:11Z" level=warning msg="Failed, retrying in 2s ... (1/3). Error: initializing source docker://debian:latest: pinging container registry registry-1.docker.io: Get \"https://registry-1.docker.io/v2/\": dial tcp 108.160.165.211:443: i/o timeout"
time="2026-02-05T14:47:43Z" level=warning msg="Failed, retrying in 2s ... (2/3). Error: initializing source docker://debian:latest: pinging container registry registry-1.docker.io: Get \"https://registry-1.docker.io/v2/\": dial tcp 108.160.165.211:443: i/o timeout"
time="2026-02-05T14:48:15Z" level=warning msg="Failed, retrying in 2s ... (3/3). Error: initializing source docker://debian:latest: pinging container registry registry-1.docker.io: Get \"https://registry-1.docker.io/v2/\": dial tcp 108.160.165.211:443: i/o timeout"
Error: creating build container: unable to copy from source docker://debian:latest: initializing source docker://debian:latest: pinging container registry registry-1.docker.io: Get "https://registry-1.docker.io/v2/": dial tcp 108.160.165.211:443: i/o timeout

I've find out the reason: My country censored DockerHub
But After using VPN of CloudFlare, Another Error appeared:

<stderr_txt>
docker_wrapper 17 starting
docker_wrapper config:
workdir: /boinc_slot_dir
use GPU: no
create args: --cap-add=SYS_ADMIN --device /dev/fuse
verbose: 1
Using WSL distro boinc-buda-runner
Using podman
running docker command: ps --all --filter "name=^boinc__lhcathome.cern.ch_lhcathome__theory_2922-4821394-491_2$" --format "{{.Names}}|{{.Status}}"
program: podman
command output:
EOM
creating container boinc__lhcathome.cern.ch_lhcathome__theory_2922-4821394-491_2
running docker command: images
program: podman
command output:
REPOSITORY TAG IMAGE ID CREATED SIZE
EOM
building image
running docker command: build "." -t boinc__lhcathome.cern.ch_lhcathome__theory_2922-4821394-491 -f Dockerfile
program: podman
read_from_pipe() error: timeout
build_image() failed: -182

</stderr_txt>

This is quite a common error. I have not managed to reproduce it myself. It would be good to know why this happens.

It doesn't repro on my computer either
Now my WUs are working quite OK

Most errors occur on the 670±1s
It's quite random