Windows: Client ping raises pywintypes.error if Docker pipe is not open
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
The DockerClient.ping() method raises a docker.errors.APIError if the daemon is not responsive, however, on Windows if Docker is not running at all or switching between Linux and Windows containers, the pipe is not open and subsequently results in
pywintypes.error: (2, 'CreateFile', 'The system cannot find the file specified.')
or
pywintypes.error: (232, 'WriteFile', 'The pipe is being closed.')
Steps to recreate:
Make sure Docker isn't running (System Tray > Quit Docker Desktop)
>>> import docker
>>> client = docker.from_env()
>>> client.ping()
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at DockerClient.ping() and trace how Windows named-pipe failures are handled when Docker is stopped or switching container modes. Reproduce the reported pywintypes.error cases and verify that the method instead raises the documented docker.errors.APIError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100