You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running docker images after pulling gives a more accurate estimate:
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
readthedocs/build latest 6b9ab0a5ddaf 12 months ago 8.86GB
...but still does not account for the temporary space needed to download, decompress, and apply layers.
On my machine, that image required approximately 10GB of space in Docker's data root (which, in the Ubuntu-packaged version, defaults to /var/lib/docker).
(See also #5553, as readthedocs/build:latest may not be the best image to use for estimating.)
Expected Result
The installation instructions should estimate the minimum amount of disk space required, so that users can make sure they are prepared before downloading several gigabytes.
Actual Result
I had to free up extra space and retry the download.
The text was updated successfully, but these errors were encountered:
Details
The instructions on setting up a Docker build environment describe pulling the build image, but give no sense of how much space will be required. The Docker Hub list of tags does not seem to accurately describe how much space the assembled image requires.
Running
docker images
after pulling gives a more accurate estimate:...but still does not account for the temporary space needed to download, decompress, and apply layers.
On my machine, that image required approximately 10GB of space in Docker's data root (which, in the Ubuntu-packaged version, defaults to
/var/lib/docker
).(See also #5553, as
readthedocs/build:latest
may not be the best image to use for estimating.)Expected Result
The installation instructions should estimate the minimum amount of disk space required, so that users can make sure they are prepared before downloading several gigabytes.
Actual Result
I had to free up extra space and retry the download.
The text was updated successfully, but these errors were encountered: