When I run docker on my laptop, the fans turn on full speed and stay there (recent macbook pro). I kill docker any time I don't expect to use it in the next hour. If I'm not on AC power, it halves my battery life. I wouldn't even consider keeping docker running constantly. Is this not the normal experience?
Docker as an Integrated Development Environment (2019)
91–93 of 93 posts
Re: Docker as an Integrated Development Environment (2019)
#92When I run docker on my laptop, the fans turn on full speed and stay there (recent macbook pro). I kill docker any time I don't expect to use it in the next hour. If I'm not on AC power, it halves my battery life. I wouldn't even consider keeping docker running constantly. Is this not the normal experience?
Same here with Docker Desktop for Windows.
Unless you have a Linux-based operating system, Docker behaves very poorly.
NB: The Hyper-V backend behave a bit less poorly than the WSL backend.
I've found that Docker Desktop uses a lot of Disk I/O whenever you use volumes, or pull an image, or anything else that touch the hard drive.
Re: Docker as an Integrated Development Environment (2019)
#93Earlier quoted context omitted.
Case in point: "Using Alpine can make Python Docker builds 50× slower", https://pythonspeed.com/articles/alpine-docker-python/
That article should be titled, “Most Python packages do not upload an Alpine-compatible wheel to PyPI.” If you know where to find Alpine-compatible wheels, or host your own, Alpine has no build-speed penalty.
Exactly zero packages upload Alpine-compatible wheels to PyPI.
The manylinux specification assumes glibc, so there is no valid distribution format which would allow the publication of non-glibc wheels.
However there is an in-progress PEP to support it: https://www.python.org/dev/peps/pep-0656/