Passing -Ddocs=disabled -Ddocs_pdf=disabled does not fix the issue:
This does seem like a bug but the build log you linked to (not inlining only relevant content in the email may be part of why this went unresponded to) doesn't show these disables and so it tried to build the documentation and failed because of the above.
The IO error seems to be environmental, outside what we can fix from a bug perspective. Following up on that in -general may yield fruit.
If you want to repost a current attempt at disabling documentation builds then seeing the aforementioned error you can do that here. That is a bug we'd be in a position to try and fix at least.
