From: DJ Delorie <dj@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [patch v1] Allow for unpriviledged nested containers
Date: Mon, 15 Nov 2021 15:58:02 -0500 [thread overview]
Message-ID: <xnpmr13zmt.fsf@greed.delorie.com> (raw)
In-Reply-To: <87sfw1qz3q.fsf@oldenburg.str.redhat.com>
Florian Weimer <fweimer@redhat.com> writes:
> * DJ Delorie:
>> Florian Weimer <fweimer@redhat.com> writes:
>>> Have you tried a bind mount of the existing /proc into the chroot (from
>>> the outside of that chroot)?
>>
>> That's an interesting idea, but the directory it (and /sys, /dev, etc,
>> eventually, I suppose) needs to be mounted on doesn't exist until we're
>> late into "make check" and rsync'ing the pristine test container to the
>> working test container. And we delete and rebuild that container as
>> needed. It would be a lot of messy logic to pre-mount that.
>
> Huh. We already do this for various parts of /dev.
Ah, I thought you meant "outside of the podman container". Testing...
next prev parent reply other threads:[~2021-11-15 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 23:02 DJ Delorie
2021-11-10 8:23 ` Florian Weimer
2021-11-10 18:30 ` DJ Delorie
2021-11-12 13:31 ` Florian Weimer
2021-11-15 20:58 ` DJ Delorie [this message]
2021-11-15 22:34 ` [patch v2] " DJ Delorie
2021-11-15 22:43 ` DJ Delorie
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=xnpmr13zmt.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).