From: <rsbecker@nexbridge•com>
To: "'Michal Suchánek'" <msuchanek@suse•de>,
"'Hadmut Danisch'" <hadmut@danisch•de>
Cc: <git@vger•kernel.org>
Subject: RE: Git destroys u+s and g+s directory modes
Date: Sat, 27 Dec 2025 09:27:26 -0500 [thread overview]
Message-ID: <008901dc773c$f05508c0$d0ff1a40$@nexbridge.com> (raw)
In-Reply-To: <aU_lqe2Z47STv68O@kitsune.suse.cz>
On December 27, 2025 8:57 AM, Michal Suchánek wrote:
> On Sat, Dec 27, 2025 at 03:37:51AM +0100, Hadmut Danisch wrote:
> > Hi,
> >
> > (please respond to my e-mail as well, not just to the list, I'm not
> > subscribed),
> >
> >
> > I do have a problem with git 2.43.0 (ubuntu server 24.04.3) and
> > directory
> > modes:
> >
> >
> > I do need my git repo (owned by me) to be readable by a system user
> > (running a rootless podman container).
>
> When you want it to be readable you do not need any special permission
bits.
>
> You can set the directories and files to be readable by group, and ensure
the
> container user is part of the group.
>
> You are porbably looking for core.sharedRepository configuration option.
>
> If git is particularly unhappy accessing a readonly repository and the
container is
> short-lived you can add an overlay over the repository when creating the
> container.
There is an option with ubuntu: Access Control Lists (ACLs). These provide
override security for directories that might assist in your process without
having to worry about git security settings. It might be worth looking into
this option.
Randall
next prev parent reply other threads:[~2025-12-27 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-27 2:37 Git destroys u+s and g+s directory modes Hadmut Danisch
2025-12-27 13:56 ` Michal Suchánek
2025-12-27 14:27 ` rsbecker [this message]
2025-12-27 14:40 ` Hadmut Danisch
2025-12-27 15:12 ` Andreas Schwab
2025-12-27 15:19 ` rsbecker
2025-12-27 21:49 ` Gabor Gombas
2025-12-27 14:44 ` Hadmut Danisch
2026-01-02 7:55 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='008901dc773c$f05508c0$d0ff1a40$@nexbridge.com' \
--to=rsbecker@nexbridge$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=hadmut@danisch$(echo .)de \
--cc=msuchanek@suse$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox