Hello,
On 29 Aug 2024, at 14:00, sio / siosios1@hotmail.com wrote:
Michael Tremer wrote:
Hello sio, The build system does not have any network access. We block this so that any compromised package cannot download anything more malicious that we don’t have a paper trail for. It is also that not all build systems have internet access all the time. So you will have to download everything you need through the lfs/netdata file, extract, and then run the build. In the “./make.sh shell” environment we make network access possible so that you can download files and patches and what not. -Michael
On 29 Aug 2024, at 02:07, sio / siosios1@hotmail.com wrote: I ran two separate builds on two different machines from scratch and they ran through the build process no problems that i could tell. I also added the netdata package to the mix on a second run on one of the machines and failed the build with the below error. mind you i have a 3rd machine with CU187 on it and it built the netdata package flawlessly, same files as I used on the CU188 machine so I am not sure if this is from the change or not. I have also gone into the shell with make.sh on the machine that had the error and could build netdata just fine with the same commands as in the lfs file. netdata build from shell: --- We are done! --- ^ |.-. .-. .-. .-. .-. . netdata .-. .-. .-. .-. .-. .- | '-' '-' '-' '-' '-' '-' '-' '-' '-' '-' +----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+---> --- is installed now! --- enjoy real-time performance and health monitoring... ipfire build chroot (x86_64) root:~/netdata-v1.47.0$ Ping from shell: [root@cloud ipfire-2.x]# ./make.sh shell Entering to a shell inside the build environment, go out with exit ipfire build chroot (x86_64) root:~$ ping github.com PING github.com (140.82.116.3) 56(84) bytes of data. 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=1 ttl=52 time=110 ms 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=2 ttl=52 time=89.0 ms 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=3 ttl=52 time=112 ms 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=4 ttl=52 time=109 ms 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=5 ttl=52 time=102 ms 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=6 ttl=52 time=101 ms 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=7 ttl=52 time=110 ms 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=8 ttl=52 time=106 ms Error: netdata (1.47.0) [ 1:36 ][ FAIL ] Could not resolve host: github.com shutting down connection #0 --- LOG END --- error: downloading 'https://github.com/netdata/kernel-collector/releases/download/v1.4.5.1/netda...' failed status_code: 6 status_string: "Could not resolve hostname" log: --- LOG BEGIN --- Could not resolve host: github.com shutting down connection #0 --- LOG END --- ninja: build stopped: subcommand failed. FAILED '' ABORTED Failed to build Netdata. make: *** [netdata:86: /usr/src/log/netdata-v1.47.0] Error 1 make: Leaving directory '/usr/src/lfs' ERROR: Building netdata
hello Michael,
ok, that would make sense but was there a changed in 188 vs 187? just asking due to being able to build the same identical package on 187, if there wasn't a change then i need to do some more investigating. thank you for the info you can provide on this.
Yes, this has changed in the current development cycle. There is more information about that here:
https://lists.ipfire.org/hyperkitty/list/development@lists.ipfire.org/messag...
-Michael