Closed erhan- closed 5 years ago
It seems that its a machine-specific bug. Your deployment caught my eye:
The docker-image runs inside a VM and resources seem not to be exhausted.
How much memory are you allocating to docker inside that VM?
I have a different issue but it might come from the same problem.
Here my final log: fatal: fork: Cannot allocate memory
.
How much memory is needed to build lineageos? I have 6 Gigs on my server.
I don't know for sure, my problem was always disk space because I didn't had that much. But 6Gigs sounds kinda low.
When I talk about memory, I'm talking about RAM.
How much RAM is needed?
I'm not entirely sure, but I would say 8Gigs up would be better.
We can keep continuing the discussion but since I think this a machine-related problem I'm closing the issue. Feel free to reopen if you think there is something going on with this docker image.
@jfloff I have not been online for a while. I am pretty sure that this is a machine issue so this can stay closed imho. Thanks!
Hey @jfloff ,
I am trying to build los-15.1 for the LG v20 (H990) and am having problems when it starts building the kernel. I get segmentation faults:
my device-config:
I could not find a way to fix this problem. I even changed to "unstable" in the debian image to use newer gcc binaries but that did not work either.
The docker-image runs inside a VM and resources seem not to be exhausted.