Yann E. MORIN
893bd56974
Our utils/docker-run wrapper is needed to provide a reproducible build environment: tools, variables, etc... but is not meant for isolation. As such, we do not care which network configuration is used. In some settings (e.g. enterprise networks), it is often the case that a VPN is in use, especially in those wonderful times of widespread remote work. Letting Docker decide on the network setup will most usually lead to it creating a private network that is NATed onto the principal network interface, leading to non-functional network in the container when a VPN is in use. As such, always use the host network configuration, and do not let Docker create a private network for the container. Signed-off-by: Yann E. MORIN <yann.morin@orange.com> Cc: Ricardo Martincoski <ricardo.martincoski@datacom.com.br> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on OFTC IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches