build in docker container #250
Comments
|
I think your container needs more than just the build directory. At least board, configs and package are needed. If you really want to use docker, then I would have the whole git repo as a volume. @ski7777 plans some cleanups so your plan might work one day. |
|
I actually did mount the entire repo into |
|
I guess you checked already that the uid of the br-user is the same as the one who checked out the ftcommunity repo? Is there any message from docker itself (maybe that it prevented execution of the cross compiler)? For further analysis please provide the full output of a complete build (not just the error message) so someone can compare how it differs from a regular build. |
|
thanks for the hint, I also checked the user and permissions. Above provided log is the complete build log. |
|
I could not reproduce your docker setup - to me it fails before it starts compiling: |
|
@hypnotoad yes, sorry |
|
To me, the idea to build in a standardized docker environment seems good because that would hopefully rule out external errors and maybe also extend the developer basis. It would be great if we could eventually add the Dockerfile and the docker-compose to the git (maybe in a subdirectory). Regarding the issue: Did you use the new docker buildkit (export DOCKER_BUILDKIT=1) or the old system which first copies >20GB into the container? I am just trying the DOCKER_BUILDKIT=1 in the master branch and it seems to compile fine. |
|
|
When I tried to build an updated release, I also had problems. @MichaelSp : Could you try to delete the container and re-build from scratch? I have the impression that building a second time does not work properly. |
|
Few questions to make our results comparable:
I'm still not able to build with a clean container:
|
|
So it fails right after starting to compile? To reproduce the problem better, I created a branch "docker" from master with your docker-compose.yml and the Dockerfile, but with no further change. I try this checkout from scratch and report later if it worked: |
|
My first build as above worked and created the correct files in As I had similar problems, I could assume that mixing the |
|
Thank you very much @hypnotoad for your extensive analysis and the concrete steps you did to build the images. I still get this error message on my side:
Here is the full build log: https://gist.github.com/MichaelSp/8b52708516511735d11f0762a7298293 I'm running on MacOS M1 Pro |
|
I think this here is where things start going wrong: I don't have this warning. After the compilation, my buildroot/.config has All of your warning lines are due to the external modules. To me, the docker-compose.yml looks ok regarding hardlinking or "mv" problems, but I could imagine that the |
|
What is the state of this development? |
|
Just tried it on the latest |
I try to build the firmware inside a docker container (not to mess up my system). But for some reason it does not work. Any idea how to run the build inside docker?
I tried it in
masterbranch:and in
nextbranch:Build root not found. I assume some PATH is missing:
Cannot execute cross-compiler '/arm-linux-gcc'For some reason the toolchain is not found / built.
Appendix
DockerfileSince I mounted the
/buildfrom outside, the hard-link didn't work and I had to patch this file in/build/buildrootrunning it with
docker-compose.yamlThe text was updated successfully, but these errors were encountered: