Update readme to explain mystery build error is usually a memory one. #2367
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The root cause of the failures I've been seeing running the Jekyll build in a container is the process running out of memory and being silently killed. I spent a while playing with the compose file to allocate more memory, but this doesn't help if the podman machine hasn't been created at a non-default size. I can't find a mechanism to give a more informative error (podman just silently kills the process, presumably in response to an allocation request outside the limit). I also can't find a way to detect the "minimum memory request is bigger than the container runtime is giving us" situation early and fail fast.
So all I can do is document. :(