case about nRF Connect SDK install on ubuntu 22.04.5 server

[peter.min]

Hi,

1. Using VS Code plugin remote ssh to access the nRF Connect SDK environment on ubuntu server on windows, the board cannot be found.
2. Please help me troubleshoot the settings configuration file on ubuntu and see how to configure it correctly
3. The ncs version is v2.9.0

The error message is as follows. I think this is the problem

Kind regards,
Peter.Min

[Amanda Hsieh]

Hi, 

Please provide the Support log via the right top in the Welcome view.

Regards,
Amanda H.

[peter.min]

Hi Amanda Hsieh,

any update?

Kind regards,
Peter.Min

[peter.min]

Hi Amanda Hsieh,

any update?

Kind regards,
Peter.Min

[Amanda Hsieh]

Not yet. 

[Amanda Hsieh]

Is there a reason why it is set as the following figure? 

[peter.min]

Hi  Amanda Hsieh,

1. These are automatically generated and not set by me.

Kind regards,
Peter.Min

[Amanda Hsieh]

Hi, 

The team was able to reproduce this.

Some assumptions:

• SDK and Toolchain both installed in /opt/ncs

sudo addgroup toolchains
sudo usermod -a -G toolchains user2
sudo usermod -a -G toolchains user1
sudo chgrp  -R toolchains /opt/ncs/

At this stage, we get to the same issue as the user were user1 can see the boards and user2 cannot. Under the hood the error is  

fatal: detected dubious ownership in repository at ...`

To fix this, we had to run  

git config --global --add safe.directory '*' 

 

NOTE:

Before disabling, make sure you understand this security measure, and why it exists. You should not do this if your repositories are stored on a shared drive.

However, if you are the sole user of your machine 100% of the time and your repositories are stored locally, then disabling this check should, theoretically, pose no increased risk.

Also note that you can't currently combine this with a file path, which would be relevant in my case. The command doesn't interpret the wildcard * as an operator per se – it just takes the "*" argument to mean "disable safe repository checks/ consider all repositories as safe".  (https://stackoverflow.com/questions/72978485/git-submodule-update-failed-with-fatal-detected-dubious-ownership-in-reposit)

Have not tried this out but it seams user can also use git's --shared 

https://git-scm.com/docs/git-init#Documentation/git-init.txt-code--sharedfalsetrueumaskgroupallworldeverybodyltpermgtcode

An alternative solution is for the user to checkout the SDK for each user.