Repository navigation
Windows NanoServer CI needs recovery when the Docker daemon fails to start #1330
Description
Run: https://github.com/astral-sh/uv-dev/actions/runs/34497082623
Job: https://github.com/astral-sh/uv-dev/actions/runs/34497082623/job/102940339897
Workflow: CI
Job: test-integration / windows nanoserver
Platform: windows-latest (Microsoft Windows Server 2025, windows-2025-vs2026)
Attempt: 1
The job failed before starting the NanoServer container or executing uv:
failed to connect to the docker API at npipe:////./pipe/docker_engine; check if the path is correct and if the daemon is running: open //./pipe/docker_engine: The system cannot find the file specified.
astral-sh#18713 restored this integration job with a direct docker run invocation and no Docker service readiness or recovery step. actions/runner-images#13729 tracks the same intermittent startup failure on GitHub-hosted Windows runners, including Windows 2025, and documents restarting the Docker service as a workaround. A bounded service-start/recovery step would prevent this infrastructure flake from failing main.
#543 tracked the identical symptom but was closed when astral-sh#20961 removed the test. The restored job makes this a new recurrence. astral-sh#18663 is distinct because this run never reached the uv behavior that the NanoServer test exercises.
Activity
astral-automations-bot commentedon Sep 10, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/34505796414
astral-automations-bot commentedon Sep 10, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv/actions/runs/34509107714
This sample occurred in astral-sh/uv main on windows-2025-vs2026; the tracker’s initial sample was from astral-sh/uv-dev, with the same job and missing Docker pipe.
astral-automations-bot commentedon Sep 10, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/34521359486
astral-automations-bot commentedon Sep 11, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/34584703639
astral-automations-bot commentedon Sep 11, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv/actions/runs/34584682168
astral-automations-bot commentedon Sep 11, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/34601090900
astral-automations-bot commentedon Sep 11, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/34601090900
Attempt 2 on windows-2025-vs2026 failed with the same missing Docker named pipe as attempt 1, so the workflow retry did not recover the daemon.
astral-automations-bot commentedon Sep 11, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/34623681814
astral-automations-bot commentedon Sep 11, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/34632130593
astral-automations-bot commentedon Sep 11, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/34634358655
astral-automations-bot commentedon Sep 11, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv/actions/runs/34648507613
astral-automations-bot commentedon Sep 12, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/34699605439
astral-automations-bot commentedon Sep 12, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/34699605439
astral-automations-bot commentedon Sep 12, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/34721893533
107 remaining items
astral-automations-bot commentedon Oct 8, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/37721420945
astral-automations-bot commentedon Oct 8, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv/actions/runs/37790511080
astral-automations-bot commentedon Oct 8, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/37807409395
astral-automations-bot commentedon Oct 8, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv/actions/runs/37807349248
astral-automations-bot commentedon Oct 8, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv/actions/runs/37807384131
astral-automations-bot commentedon Oct 8, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv/actions/runs/37810440899
astral-automations-bot commentedon Oct 8, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/37814196225
astral-automations-bot commentedon Oct 8, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/37816356866
This occurrence also independently reproduces #815: the Deadsnakes Python 3.9 job exhausted its 15-minute limit during APT setup after successful PPA metadata downloads. Its cancelled conclusion is an independent timeout: https://github.com/astral-sh/uv-dev/actions/runs/37816356866/job/113448686018
astral-automations-bot commentedon Oct 9, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/37860761861
astral-automations-bot commentedon Oct 9, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/37860761861
astral-automations-bot commentedon Oct 9, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/37860761861
astral-automations-bot commentedon Oct 9, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/37967243271
astral-automations-bot commentedon Oct 9, 2026
Another workflow run encountered this failure: https://github.com/astral-sh/uv-dev/actions/runs/37970436486
zaniebot commentedon Oct 15, 2026
Fixed by astral-sh#22449, which starts Docker when the service is not running before launching the NanoServer container.