Codebuild Stopping At Filesystem Boundary Git Discovery Across Filesystem Not Set

Sudo cp r original repo backup repo cd backup repo git status fatal.

Codebuild stopping at filesystem boundary git discovery across filesystem not set. Not a git repository or any parent up to mount parent home kozi stopping at filesystem boundary git discovery across filesystem not set. Continuum akshay jadhav changed the title a container name must be specified for pod airflow t scheduler 6c484cc477 5gnq5 choose one of. Abi bionic bootable build cts dalvik development device docs external. Not a git repository or any parent up to mount point stopping at filesystem boundary git discovery across filesystem not set.

Armin novak added a comment 2015 11 23 08 54 couldn t this and the necessity for a checked out revision be solved by using the git ls remote command. Root proton cd usr root proton usr git pull fatal. The machine is not using utf 8 or en us utf 8. Not a git repository or any parent up to mount point stopping at filesystem boundary git discovery across filesystem not set.

In my case our sys admin had decided that the apache2 directory needed to be on a mounted filesystem in case the disk for the server stopped working and had to get rebuilt. I came into this issue when i copy my local repository. Not a git repository or any parent up to mount point stopping at filesystem boundary git discovery across filesystem not set. Please help me out.

The configured locale does not work well in the machine this is caused by bamboo server being unable to access the git directory in the local repository cache. Not a git repository or any parent up to mount point data stopping at filesystem boundary git discovery across filesystem not set. You can turn off the behavior and and warning by exporting git discovery across filesystem 1. Ran across this page and several like it all talking about the git discovery across filesystem not set message.

It s probably because you are building a gem from source and the gemspec shells out to git like many do today so you ll still get the warning fatal. Coming here from first google hit. Root proton usr cd etc root proton etc git pull fatal. Please don t do this as a solution until you understand both how your filesystems are layed out and what the git discovery across filesystem variable does.

On heroku if you heroku config set git discovery across filesystem 1 the warning will go away. Not a git.