-
Notifications
You must be signed in to change notification settings - Fork 101
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
ownership issue #300
Comments
ownership permissions
|
related go-gitea/gitea#19455 maybe klaus should also be able to act as a user UID? |
I actually didnt know that docker can set this with the -u flag. It works perfectly when I set |
Thanks for reporting and debugging! I don't understand what's the root cause here, can you please attempt to explain it a bit more elaborately? |
the git commands don't work if the git folder does not belong to the operating user ie: the docker container |
This is behaviour in newer versions of git, see https://github.blog/2022-04-18-highlights-from-git-2-36/#stricter-repository-ownership-checks |
@jelmer do you think this is a proper fix to this problem? I don’t have time to think about this right now so would trust your call |
The proposed fix works, but it assumes that the repositories being served are owned by the current user. If we go that route though, we'd probably want to hide or grey out the repositories not owned by the current user rather than letting git itself fail - which is not visible to the end user. An alternative would be to just disable this feature in the docker container. |
Thanks, that's helpful. I think in this case it's better to just disable the feature: the Docker container is meant for getting started quickly, not for production workloads, and the old behaviour is much less annoying if you don't care about security. |
As an aside, I think it would be great if the docker image was more production ready. I personally run Klaus in Kubernetes, for example. |
I'm happy to merge any improvements. I don't use klaus a lot these days and when I use it then it's exclusively on a local dev machine |
As of Git 2.36:
|
Doesn't seem to like my cloned repositories unless I run
docker exec run git config --global --add safe.directory [repo]
on itThe text was updated successfully, but these errors were encountered: