fatal: detected dubious ownership in repository at '/opt/MCRIBS'
#390
-
Busy day.. Sorry in advance but I'm going to start initiating threads here as I run into issues that I think might warrant a fix/improvement. If that is confirmed by the team, then I'll escalate it to a ticket. If not then I think at least it can still be helpful to someone in the future, assuming I'm not the only one that will run into these issues! First up in a slew of permissions errors I've been running into today. Running The latest Nibabies via singularity on an HPC: command
I got this Full Stack trace
For me the work around was entering the container and adding the suggested exception for the MCRIBS repository i.e. singularity shell --cleanenv /home/path/to/nibabies_latest.sif git config --global --add safe.directory /opt/MCRIBS And FWIW I initially thought it might be a permissions issue, but the permissions of the directory look fine ls -l /opt drwxr-xr-x 8 root root 222 Jul 11 13:55 MCRIBS crash-20240905-165240-hubers2-mcribs_recon-d77c9839-6a40-4e83-a1db-ce6d84aef7fe.txt |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
IIRC, the message
is just a warning that gets printed to the log, not the actual reason for the crash - probably since we are git cloning in the MCRIBS container and then copying it over for the nibabies one. I think it can be resolved by adding that command ( In your case, looks like there was a problem with loading the segmentations.
|
Beta Was this translation helpful? Give feedback.
IIRC, the message
is just a warning that gets printed to the log, not the actual reason for the crash - probably since we are git cloning in the MCRIBS container and then copying it over for the nibabies one. I think it can be resolved by adding that command (
git config --global --add safe.directory /opt/MCRIBS
) directly into the Dockerfile.In your case, looks like there was a problem with loading the segmentations.