Been building images for a while. Recent change was in the build script to use “generic” instead of “iso”. I made that adjustment but my build fails. Git repo pull and local docker image are all up to date. Trying to build current 1.5. Failure is this:
[2024-08-21 23:15:10] lb chroot_install-packages install
P: Begin installing packages (install pass)...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package linux-image-6.6.47-amd64-vyos
E: Couldn't find any package by glob 'linux-image-6.6.47-amd64-vyos'
E: Couldn't find any package by regex 'linux-image-6.6.47-amd64-vyos'
E: An unexpected failure occurred, exiting...
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Traceback (most recent call last):
File "/vyos/./build-vyos-image", line 621, in <module>
cmd("lb build 2>&1")
File "/vyos/scripts/image-build/utils.py", line 84, in cmd
raise OSError(f"Command '{command}' failed")
OSError: Command 'lb build 2>&1' failed
I edited data/defaults.toml to use kernel 6.6.45, as that was the last version 2 days ago. But the update was made to that file for 6.6.47 2 days ago, why does it not exist yet? What’s the expectation there?
Since the kernels and other packages are built nightly (if changed) I would expect it to be 24-48 hours before your custom build would work without errors.
Like if the kernel used is changed at lets say 01:00 in the morning on day 1 then your custom compile using this kernel wont work until at 02:00 or such at day 2 (dunno how long it will take for the compileserver to compile the new kernel or for that matter when during the nights the compileservers are doing their thing).
Its like a chicken or the egg problem
The new kernel wont get compiled until the source telling the compile servers to compile the new kernel is updated and the compile servers does their thing once a day (dunno at which time during the nights).
This wouldnt be a problem if VyOS used vanilla kernel from Debian but since there are custom changes made (among with modules being compiled etc) you end up with this “chicken or the egg” problem where the source points to a new kernel where its packages currently doesnt exists at the repo.
A workaround is if you build the kernel manually and place the resulting deb files at the root of the build container where it will look for local cached deb’s.
