Closed Doom4535 closed 3 years ago
@Doom4535 Are you able to navigate into these directories ?
Hello @Doom4535 ,
This working as intended - the symlinks are unfortunate though. The idea of building within the Docker container is to keep the Bazel workspace/outputs within that container. When running via docker-build, once the build completes the outputs are copied to the out/ folder that is external to the Docker container - the Bazel intermediate files are not.
If you want to see all these files you can jump into the docker container using:
make docker-shell
(inside Docker) make libedgetpu
When I run a build with Docker, it seems that final clean phase is incomplete, as several broken symbolic links are left behind:
I suspect this is because bazel cleans the catch (in this case
eab0d61a99b6696edb3d2aff87b585e8
) after the build finishes successfully, which breaks the symbolic links.Build command:
DOCKER_CPUS="k8" DOCKER_IMAGE="ubuntu:18.04" DOCKER_TARGETS=libedgetpu make docker-build
Docker Version:Docker version 20.10.6, build 370c28948e