According to the docs, we should get around 18GB worth of disk space available on ppc64le.
Running/Building containers using the included docker service fails with “disk quota exceeded” well before the 18GB limit (in fact 9GB).
This can be seen this pypa/cibuildwheel job or this pypa/auditwheel job. This pypa/cibuildwheel job has
df -h logging to help understand the issue.
The fact that the tests ran in these job would require 9GB worth of disk was also kind of worrying. I did an experiment to run all of those tests using a rootless docker service instead:
- This pypa/cibuildwheel job runs perfectly showing a disk usage which increased by ~1.5GB which is what I would expect (the peak usage is certainly higher, but not 7.5GB higher).
- This pypa/auditwheel job also runs perfectly showing a disk usage which increased by ~1.6GB (the peak usage is certainly higher, and higher than for the cibuildwheel job, but not as high as to reach the limit)
IMHO, Travis CI should offer the option to run rootless docker or podman in LXD builders. It certainly helps with some permission issues (c.f. Ppc64le docker buildx permission issues depending on which group of workers the job runs on - #3 by mayeut) and would have helped here.
Wether we’re talking about podman or rootless docker, it’s challenging to set those up in a generic way on all those “exotic” platforms and incurs a maintenance cost on projects working around the “native docker service” limitations offered by Travis CI which should thus be fixed by providing alternatives.
What’s Travis CI opinion to these observations ?