0bb9dcce19
Leaving the user as coreboot caused the entrypoint to run as coreboot, which means we couldn't mount directories or run sshd correctly. Switching to root at the end of the file fixes this. Signed-off-by: Martin Roth <gaumless@gmail.com> Change-Id: Ie10e1d7ad4def0faafe3bcd580a77e23c3bfe948 Reviewed-on: https://review.coreboot.org/c/coreboot/+/79067 Reviewed-by: Felix Singer <service+coreboot-gerrit@felixsinger.de> Tested-by: build bot (Jenkins) <no-reply@coreboot.org> |
||
|---|---|---|
| .. | ||
| 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