162b6484ff
Instead of installing the pip modules system-wide, and possibly causing conflicts, install them into a virtual environment for the coreboot user. If we wanted to, in the future, we could install different versions of the modules into different virtual environment directories to allow for testing or anything else we needed. Change-Id: I49c749a13a698bfb7af29bf07e42ac14b67b2ae7 Signed-off-by: Martin Roth <gaumless@gmail.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/79006 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Felix Singer <service+coreboot-gerrit@felixsinger.de> |
||
|---|---|---|
| .. | ||
| Dockerfile | ||
| README.md | ||
| authorized_keys | ||
README.md
This builds the coreboot tree in /dev/cb-build so that's a directory that uses a tmpfs. This helps to speed up the build and doesn't write the output to the SSD.
The encapsulate tool that the coreboot build runs under for security requires that docker be run using the --privileged command to work correctly.
Run with the command:
docker run --privileged --restart=always -d -p 49151:49151 -v $host_path_to_ccache:/home/coreboot/.ccache -v $host_path_to_data_cache:/data/cache coreboot/coreboot-jenkins-node