error while using docker for mac client 2.5.0.0
See original GitHub issueUsing python 3.8.5 and docker-py version 4.3.1
File "/Users/mmoskwa/.local/share/virtualenvs/lunchbox-5JMc0Mx2/lib/python3.8/site-packages/docker/models/containers.py", line 887, in get
resp = self.client.api.inspect_container(container_id)
File "/Users/mmoskwa/.local/share/virtualenvs/lunchbox-5JMc0Mx2/lib/python3.8/site-packages/docker/utils/decorators.py", line 19, in wrapped
return f(self, resource_id, *args, **kwargs)
File "/Users/mmoskwa/.local/share/virtualenvs/lunchbox-5JMc0Mx2/lib/python3.8/site-packages/docker/api/container.py", line 771, in inspect_container
self._get(self._url("/containers/{0}/json", container)), True
File "/Users/mmoskwa/.local/share/virtualenvs/lunchbox-5JMc0Mx2/lib/python3.8/site-packages/docker/utils/decorators.py", line 46, in inner
return f(self, *args, **kwargs)
File "/Users/mmoskwa/.local/share/virtualenvs/lunchbox-5JMc0Mx2/lib/python3.8/site-packages/docker/api/client.py", line 228, in _get
return self.get(url, **self._set_request_timeout(kwargs))
File "/Users/mmoskwa/.local/share/virtualenvs/lunchbox-5JMc0Mx2/lib/python3.8/site-packages/requests/sessions.py", line 543, in get
return self.request('GET', url, **kwargs)
File "/Users/mmoskwa/.local/share/virtualenvs/lunchbox-5JMc0Mx2/lib/python3.8/site-packages/requests/sessions.py", line 530, in request
resp = self.send(prep, **send_kwargs)
File "/Users/mmoskwa/.local/share/virtualenvs/lunchbox-5JMc0Mx2/lib/python3.8/site-packages/requests/sessions.py", line 685, in send
r.content
File "/Users/mmoskwa/.local/share/virtualenvs/lunchbox-5JMc0Mx2/lib/python3.8/site-packages/requests/models.py", line 829, in content
self._content = b''.join(self.iter_content(CONTENT_CHUNK_SIZE)) or b''
File "/Users/mmoskwa/.local/share/virtualenvs/lunchbox-5JMc0Mx2/lib/python3.8/site-packages/requests/models.py", line 754, in generate
raise ChunkedEncodingError(e)
requests.exceptions.ChunkedEncodingError: ('Connection broken: IncompleteRead(0 bytes read)', IncompleteRead(0 bytes read))
Issue Analytics
- State:
- Created 3 years ago
- Reactions:24
- Comments:25 (7 by maintainers)
Top Results From Across the Web
Docker won't run on Big Sur | Apple Developer Forums
Docker won't start on Big Sur. Has anyone else tried it? I'll re-install to see if that helps, but Docker doesn't start right...
Read more >Docker Desktop for Mac 2.x release notes
Fixed an issue that caused Docker Desktop to crash on MacOS 11.0 (Big Sur) when VirtualBox was ... Docker Desktop 2.5.0.0 contains a...
Read more >Docker Desktop release notes
Fixed an issue preventing the creation of Dev Environments on new Mac installs and causing error "Cannot connect to the Docker daemon at...
Read more >Docker Desktop for Mac 3.x release notes
Fixed error showing stderr log in the UI. Fixes docker/for-mac#5688. Fixed an issue which caused riscv64 emulation to fail on Docker Desktop.
Read more >Overview | Docker Documentation
In the Console app . Mac provides a built-in log viewer, named Console, which you can use to check Docker logs. The Console...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hello, same/similar issue.
Python version: 3.8.6 Docker version: 2.5.0 docker-py version: 4.3.1 urllib3 version: 1.25.11
reproducer:
expected result: Exception at docker api level (
docker.errors.NotFound
ordocker.errors.APIError
)result:
We use this pattern to check if a container exists already before starting a container or when fetching the status of a container, as our software uses deterministic container names. In the case where the container isn’t running we catch
docker.errors.NotFound
, which is now broken as @mconcas points out. After initial testing, it does appear this is the only place in the API that is broken like this.A very temporary fix is catching the unexpected error, again this is unexpected, fragile, and possibly not useful for everyone’s use case: