Process exited with code 2ĭocker-compose -f. Before TeamCity 2018.1.2: docker system prune -a Service Message to Report Pushed Image. mkdir: cannot create directory `/home/projects/build': Permission denied Since TeamCity 2018.1.2: docker system prune -volumes Works for Docker v.17.06.1 or later. make/at91boot.mk:23: warning: ignoring old commands for target `/Makefile' make/u-boot.mk:31: warning: overriding commands for target `/Makefile' make/cross-gdb.mk:12: warning: ignoring old commands for target `/home/projects/build/platform/gdb-7.0.1/.source' make/gdb.mk:13: warning: overriding commands for target `/home/projects/build/platform/gdb-7.0.1/.source' Any thoughts on how the permissions work on a docker container in a Teamcity build job? Creating dockerbuild_supernova_run. Probably not project because all that works in the non TC build. You can enforce starting Docker commands on a TeamCity agent via sudo. ? Is it TC user that needs permissions or root or the user project. I dont quite understood who needs permissions here to create /home/projects/build. One way to attach to a running Docker container is by using the docker attach command. RUN apt-get update
0 Comments
Leave a Reply. |