Closed dan1d closed 1 year ago
I am also having this issue. Getting quite frustrated because neither Vagrant nor Codespaces are working for me.
It seems 32 GB is not enough. But AFAICT this is the maximum available under the free plan.
Does mastodon really take up 32gb? If so that seems like an issue in and of itself...
No. The source code takes up about 50 MB at most, the full git history takes up 561 MB, and node_modules
takes up 870 MB.
You're also installing Ruby, Postgres, Redis and possibly Elasticsearch but even all combined won't be anywhere near 32 GB.
I'm not sure how it adds up to 32 GB, but on my local machine, the LibreTranslate volume alone uses 5 GB. AFAIK the language model is downloaded when the container first boots.
I have created PR #26382 for disabling the non-essentional services (Elasticsearch and LibreTranslate) on Codespaces.
Awesome. I approved the PR but it looks like you will need approval from someone with write access before it can be merged.
I know this was closed as completed but it is happening again as of a few days ago.
I know this was closed as completed but it is happening again as of a few days ago.
I figured out why this was happening. For some reason whenever I created a new codespace by clicking the +
button in the codespaces dropdown, it was by default selecting the "mastodon on local machine" option under "Dev container configuration".
I didnt realize this until I tried creating one using the "New with options" dialog and saw the "Mastodon on local machine" selection was checked by default.
The solution for me was to go into the ["New with options" dialog] when creating a new Codespace, and then making sure to select the Mastodon on GitHub Codespaces configuration
Hope this helps someone!
Steps to reproduce the problem
Expected behaviour
Not error raised
Actual behaviour
There was an error while trying to write
Detailed description
Is there anything missing that I need to do while creating the workspace on github? I have 32gb of storage.
Specifications
main branch