Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

200GB doesn't seem to be enough space on Windows as of UE4 4.25 #112

Closed
TBBle opened this issue Nov 5, 2020 · 3 comments
Closed

200GB doesn't seem to be enough space on Windows as of UE4 4.25 #112

TBBle opened this issue Nov 5, 2020 · 3 comments

Comments

@TBBle
Copy link
Collaborator

TBBle commented Nov 5, 2020

Breaking out of #99 (comment) for visibility: It seems like the 200GB sandbox size in the ue4-docker setup and manual Windows 10 instructions is not large enough for UE 4.25.

Experiments and user reports in #99 suggest that even 400GB might not be sufficient, but 600GB has been successful.

The largest intermediate layer in my (incomplete) build of ue4-minimal on Windows 10 2004 is 263GB, with nothing excluded. I didn't watch closely enough to observe a peak disk usage. I expect all subsequent layers in the build to be smaller, as this is the last state of the "builder" target, before we start using COPY --from=builder to assemble the clean final image.

Since free disk space inside is limited by the free disk space on the host drive, setting this too high doesn't seem too risky, as you cannot over-commit. At worst, you would fill your hard disk, the build fails, and then Docker cleans up all the temp stuff and you're back to simply low on disk space.

@dkmartov
Copy link

dkmartov commented Nov 7, 2020

Out of curiosity do you think this is the same error I am getting in #110 ?
I would be good if the community who was working on this had a discord or something. I can make one and make Adam mod if people are interested.

@TBBle
Copy link
Collaborator Author

TBBle commented Nov 7, 2020

Replied on that issue.

@adamrehn
Copy link
Owner

@TBBle agreed. I've bumped it to 400GiB in commit a29ae6c and updated the docs to match. Once all of these frustrating filesystem bugs are resolved for Windows containers and things can be tested properly without risk of conflation then we can re-assess and determine whether 400GiB is sufficient or if it needs to be bumped further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants