From: DJ Delorie <dj@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org, joseph@codesourcery.com, carlos@redhat.com
Subject: Re: V8 test-in-container patch
Date: Fri, 17 Aug 2018 02:14:00 -0000 [thread overview]
Message-ID: <xnr2ixg2nh.fsf@greed.delorie.com> (raw)
In-Reply-To: <a037541e-a394-9a71-fbee-67597f65366f@redhat.com> (message from Florian Weimer on Thu, 16 Aug 2018 20:54:43 +0200)
Florian Weimer <fweimer@redhat.com> writes:
> Please have a look at misc/tst-ttyname. It uses a bind mount to put
> /proc into the chroot, and it does not have this problem.
So that gets past the /proc mount, but if you bind mount /proc, it's in
the wrong namespace and you can't fix the UID map:
error: test-container.c:948: can't write to /proc/self/uid_map
Without the uid map, you don't own your own files in the new namespace.
Like I said, fragile :-P
next prev parent reply other threads:[~2018-08-17 2:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 17:59 DJ Delorie
2018-08-16 18:54 ` Florian Weimer
2018-08-17 2:14 ` DJ Delorie [this message]
2018-08-17 2:53 ` Carlos O'Donell
2018-08-23 1:21 ` DJ Delorie
2018-08-23 19:58 ` Joseph Myers
2018-08-23 20:34 ` DJ Delorie
2018-08-23 20:43 ` Joseph Myers
2018-08-23 22:57 ` DJ Delorie
2018-08-23 23:31 ` Joseph Myers
2018-08-23 23:57 ` DJ Delorie
2018-08-24 14:41 ` Joseph Myers
2018-08-25 2:12 ` DJ Delorie
2018-08-25 2:22 ` Carlos O'Donell
2018-08-25 2:29 ` DJ Delorie
2018-08-25 2:40 ` Carlos O'Donell
[not found] ` <CAP5F8c+0EjtjaOSf5itJxx385r70XrjGEDWMvsdf8QDmOVVDRA@mail.gmail.com>
2018-08-25 2:56 ` Carlos O'Donell
2018-08-25 2:58 ` Jason Duerstock
2018-08-27 15:07 ` Joseph Myers
2018-10-09 9:55 ` Szabolcs Nagy
2018-10-09 15:26 ` Carlos O'Donell
2018-10-10 10:35 ` Szabolcs Nagy
2018-10-10 20:16 ` DJ Delorie
2018-10-11 10:00 ` Szabolcs Nagy
2018-10-11 12:55 ` Joseph Myers
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=xnr2ixg2nh.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.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).