Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different HPC systems and users #7566

Open
anikfal opened this issue Feb 26, 2024 · 2 comments
Open

Different HPC systems and users #7566

anikfal opened this issue Feb 26, 2024 · 2 comments

Comments

@anikfal
Copy link

anikfal commented Feb 26, 2024

  1. The Datalad dataset has been created on the Jureca server by me.
  2. Datalad itself has been built on two servers (Jureca and Juwels) by easybuild, and can be loaded by module load datalad.

Here's the issue:
On Jureca, all other users and I (as the dataset creator) have access to datalad functionalities. However, on Juwels, for other users, the error below occurs:

datalad status
It is highly recommended to configure Git before using DataLad. Set both 'user.name' and 'user.email' configuration variables.
CommandError: 'git -c diff.ignoreSubmodules=none -c core.quotepath=false ls-files --stage -z --exclude-standard -o --directory --no-empty-directory' failed with exitcode 128
fatal: detected dubious ownership in repository at '/p/largedata2/detectdata/abc'
To add an exception for this directory, call:

	git config --global --add safe.directory /p/largedata2/detectdata/abc

I don't have such an issue on Juwels. Perhaps because I was the creator of the dataset.
This problem may be handled using safe.directory by that specific user. However, how can I handle it for all users, so they don't see such an error message?

@yarikoptic
Copy link
Member

this smells like system specific issue. @loj @aqw?

@aqw
Copy link
Contributor

aqw commented Mar 22, 2024

This is a security feature of git. I don't know when it was introduced, but I noticed a change in behavior on our systems. It could be that Jureca and Juwels have different versions of git (and/or are configured differently at the system level).

As for how to disable this message automatically for the other users... the git docs say:

This config setting is only respected in protected configuration (see SCOPES). This prevents untrusted repositories from tampering with this value.

Which makes sense. Otherwise users could disable the security check for other users. Which runs counter to the purpose of the security feature. ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants