I've never used VyOS but I was wondering what the problem would be. This is what I did to build a .iso (I have no idea if it works or not, I don't have the hard

I've never used VyOS but I was wondering what the problem would be. This is what I did to build a .iso (I have no idea if it works or not, I don't have the hardware to test it on), courtesy of their manual https://docs.vyos.io/en/latest/contributing/build-vyos.html https://docs.vyos.io/en/latest/contributing/build-vyos.html: $ git clone -b sagitta --single-branch https://github.com/vyos/vyos-build $ cd vyos-build $ docker run --rm -it --privileged -v $(pwd):/vyos -w /vyos vyos/vyos-build:sagitta bash [docker] $ sudo make clean [docker] $ sudo ./build-vyos-image iso --architecture amd64 --build-by "j.randomhacker@vyos.io" This caused an error message, which I solved using the first result on Google: [docker] $ sudo mount -i -o remount,exec,dev /vyos [docker] $ sudo ./build-vyos-image iso --architecture amd64 --build-by "j.randomhacker@vyos.io" [docker] $ exit $ ls -l build/*.iso -rw-r--r-- 1 root root 502267904 jan 22 23:55 build/live-image-amd64.hybrid.iso -rw-r--r-- 1 root root 502267904 jan 23 00:04 build/vyos-1.4-rolling-202401222255-amd64.iso I picked 1.4 because that seems to be the latest LTS branch. Now, I'm not sure why it apt updated twenty times during the process, but after waiting a few minutes, I was left with what seems like a perfectly fine .ISO. Is this harder than downloading an .ISO from a website? Yes, of course. Do I expect everyone to be able to follow the manual? Probably not. But that's why there are ways to pay VyOS, this is a company doing open source after all. If you can spare some server capacity and are willing to put in effort, you could set up a script to run the build process automatically and host the ISO files for everyone to download, as long as you remove all the trademarked branding of course.