It works fine locally, but fails on the Space instance with the following error:
Not enough free space
(This happens when the rkllm converter runs.)
However, the converter (rkllm) itself is not open-sourced, so I can’t inspect exactly what it does internally. Based on monitoring on local, I noticed that the temporary files it creates (mainly inside the site-packages directory) do not fully consume the disk space — there should still be sufficient space left.
So I’m wondering:
Does Spaces impose any additional restrictions on /tmp or disk usage that might not reflect in visible usage?
Are there known hidden quotas or ephemeral filesystem behaviors that could cause this?
First of all, in Spaces, especially in Gradio spaces ('s Docker images), users only have write permissions for directories under /home/user/ (or maybe /home/). We cannot write to /tmp except for in starting process…
Also, directories starting with . (e.g. .cache/, .gitignore/) may not have read/write permissions for users.
From what I observed, both /usr/local/lib/python3.10/site-packages and /tmp are writable during runtime. I was able to write files to both locations without any permission errors.
So it seems the issue might not be caused by permission restrictions in those paths — at least in my case.
In that case, I think you can use up to 50GB without any problems…
Since the RAM of free space is 16GB, the amount you can use will decrease if swapping occurs…