This is happening inside a container, and in this container /go/bin is a volume:
https://github.com/NVIDIA/nvidia-docker/blob/master/tools/Dockerfile.build#L23

This volume maps to [...]/nvidia-docker/tools/bin on the host. After executing the build container, this directory will contain the nvidia-docker and nvidia-docker-plugin binaries. These binaries are then installed (install(1)) the usual way to the $PREFIX path (default is /usr/bin).

I'm not sure how you encountered this issue, folder nvidia-docker/tools/bin could have weird permissions on the host. Try removing it.
Also, are you running Docker the usual way with your account being part of the docker group?

I was able to recreate a similar error message using sudo make and then make install. Of course this is backward: the first command will create tools/bin for root and the second command will fail when trying to use the mounted volume.

From your initial post, it doesn't seem to be what you did, but it confirms there is something fishy on the permissions. The permissions you mentioned look fine, but you can simply erase 'tools/bin', it's not part of the git repo.

It would be interesting to know what's going on in your particular case. As a workaround you can always use the release tarball/package: https://github.com/NVIDIA/nvidia-docker/releases

@flx42 I bet I did that actually - I was trying several commands and permutations of with or without sudo and make / make install. My bad for not thinking about permissions. Thanks for identifying that.

@3XX0 Good to know. I didn't install from the deb because it was from an older commit on the repo... But now I see that the commit only impacted the cudnn dockerfile.

Thanks again for your help! This was definitely user error on my part.

Sorry to resurrect a dead thread, but I thought this was worth mentioning in case someone else runs across this.

I hit the same error as issue as issue #49 and was able to get around it by disabling selinux (setenforce 0). I was going to open a new issue, and started playing around with some other things (like permissions of the tools dir) to see if there's a workaround, but after i did the build successfully once, then set selinux back to enforcing, every build I do after that has worked. I even tried deleting and re-cloning the repo to recreate, but I can't. That bugs me, but what can you do? 😉 :