From: Gao Xiang <xiang@kernel.org>
To: Naoto Yamaguchi <wata2ki@gmail.com>, linux-erofs@lists.ozlabs.org
Subject: Re: RFC: erofs-utils:mkfs: add unprivileged container use-case support
Date: Wed, 10 Aug 2022 02:21:20 +0800 [thread overview]
Message-ID: <YvKloGeAl8R32vEx@debian> (raw)
In-Reply-To: <YvKj8aZp/6bg/Nxv@debian>
On Wed, Aug 10, 2022 at 02:14:09AM +0800, Gao Xiang wrote:
> Hi Naoto,
>
> On Wed, Aug 10, 2022 at 02:59:42AM +0900, Naoto Yamaguchi wrote:
> > Hi all.
> >
> > I investigate each read only filesystem for linux at linux container
> > use-case. The erofs is most interesting filesystem.
>
> First of all, many thanks for your interest! Yes, now EROFS is actively
> developing for container use cases as well, and we're happy to
> accept/maintain any useful features about this area!
>
> > A each files of guest root filesystem need to shift uid/gid in case of
> > unprivileged container to use uid/gid namespace. I work adding
> > uid/gid offsetting support to erofs-utils mkfs tool now.
> > Will be this patch accept in upstream community?
>
> Could you give more details about this? EROFS already supports idmapped
> mount for container use cases since 5.19, so I guess uid/gid offsets
> can be set by this?
Oh, I guess I've got this. Yeah, I'm fine to introduce something like
uid or gid offsets as two long options if needed. ;)
Thanks,
Gao Xiang
>
> I'm still somewhat new to container world, it would be helpful to drop
> more hints of this ;)
>
> Thanks,
> Gao Xiang
>
> >
> > Thanks,
> > Naoto Yamaguchi,
> > a member of Automotive Grade Linux Instrument Cluster EG.
next prev parent reply other threads:[~2022-08-09 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 17:59 RFC: erofs-utils:mkfs: add unprivileged container use-case support Naoto Yamaguchi
2022-08-09 18:14 ` Gao Xiang
2022-08-09 18:21 ` Gao Xiang [this message]
2022-08-09 18:37 ` Naoto Yamaguchi
2022-08-09 18:47 ` Gao Xiang
2022-08-11 23:04 ` Naoto Yamaguchi
2022-08-12 1:29 ` Gao Xiang
2022-08-12 1:49 ` Yue Hu
2022-08-14 2:33 ` Naoto Yamaguchi
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=YvKloGeAl8R32vEx@debian \
--to=xiang@kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=wata2ki@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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