From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 75492 invoked by alias); 17 Aug 2018 02:14:51 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 75467 invoked by uid 89); 17 Aug 2018 02:14:48 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=1.1 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS,UNSUBSCRIBE_BODY autolearn=no version=3.3.2 spammy= X-HELO: mx1.redhat.com From: DJ Delorie To: Florian Weimer Cc: libc-alpha@sourceware.org, joseph@codesourcery.com, carlos@redhat.com Subject: Re: V8 test-in-container patch In-Reply-To: (message from Florian Weimer on Thu, 16 Aug 2018 20:54:43 +0200) Date: Fri, 17 Aug 2018 02:14:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2018-08/txt/msg00368.txt.bz2 Florian Weimer 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