-
Notifications
You must be signed in to change notification settings - Fork 43
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
live-server.yam iso image build fails: Building efiboot image [*failed*] / log: "no space left on device" #795
Comments
I can confirm that manually increasing this in a local build solved this issue. (Updated it from 124M to 150M). |
Just as a note the correct yamls for the server version can be found under the release directory (so for 40250: https://download.clearlinux.org/releases/40250/clear/config/image/live-server.yaml ) I would expect any of the 40XXX version to need at at least 150M in the boot partition. They do change over time (with a tendency to grow). |
So I was referring not to the space provided in the yaml, but the actual allocation that his hard coded into clr-intstaller as mentioned in 1bdd4ec fixed for clearlinux/distribution#2914. I would recommend reopening this issue to fix. Specifically, I changed here in cmds := [][]string{
{"fallocate", "-l", "150M", tmpPaths[clrCdroot] + "/EFI/efiboot.img"}, |
Ah yes, I see I need to release a new version of clr-installer and bump it (which I'm pretty sure is why I did it last time from 100 to 124... ) |
Hello
Describe the bug
I am trying to build an iso image with clr-installer using the live-server.yaml and it fails not fully silent.
The img upfront build seems to have worked out fine.
As I cannot see any other disk running full, I would guess its this bug resurfacing?
1bdd4ec ( @djklimes @fenrus75 )
@pixelgeek is this somehow related to clearlinux/distribution#2914
To Reproduce
Building:
time TMPDIR=/root/tmp clr-installer -l 4 -c live-server.yaml
end of the log file:
ls *iso
ls: cannot access '*iso': No such file or directory
Expected behavior
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: