#yo, I noticed that when I use dagger for
ashen hull
Hey!
Thanks so much for the report, can you let us know which OS you're using and which container runtime, version, etc
violet abyss
yeah, no problem
I'm using windows
latest version of Docker Desktop... just a minute I'll get the version
ashen hull
I am assuming there is a similar screen on Windows -- but could you let me know what the value for "Virtual Disk Limit" is for you?
violet abyss
4.33.1
just a minute I need to go up and see to my son
back in a few
ok, tell you what, I'll ping you a message tomorrow as my WSL installing is totally fubared again after the file expansion thing, and I'll need to sort that out before I can reinstall Docker Desktop
would have been whatever the default setting is though as I haven't changed it
I'm wondering if ctrl + c ing out of the build might be causing it to not clear itself up properly??
also, I noticed that when running the .terminal() command in TypeScript the code will often run a later, failing command and bomb out without even opening the terminal, which is odd
I guess what you're hinting is that altering the virtual disk space limit might be a decent workaround for the moment...
ashen hull
It would be great to understand the default behavior on Windows, I don't think its a windows specific issue but its good to get the info.
I think Dagger will use up as much disk as it has access to with the cache, there is some GC that is supposed to be happening but a lot of this depends on your project and how much data it generates in a given build.
Any additional context you can provide will be helpful because were still tweaking these things
violet abyss
ok, soooo:
the default distro is Ubuntu and my wsl.conf file contains:
"[boot]
systemd=true"
and nothing else
My project is an nx project with quite a lot of different libs and apps but it is also a young project with only myself and a few other very occasional contributors, so only runs to about 50,000 lines of bespoke code
on the other hand, the package.json is bringing in a lot of packages, with 840 MB of node_modules. That still doesn't seem anywhere close to the size for the average large corporate project though, or something that the caching of should use up 170GB
total repo size at present is 1.44GB