Void Linux discussion
 help / color / mirror / Atom feed
From: Jonathan Schultz <jonathan@schultz.la>
To: Aleksey Tulinov <aleksey.tulinov@gmail.com>,
	Jonathan Schultz <jonathan@imatix.com>
Cc: Leah Neukirchen <leah@vuxu.org>, voidlinux@googlegroups.com
Subject: Re: xbps-src reposync error
Date: Thu, 27 Dec 2018 22:40:29 +0800	[thread overview]
Message-ID: <378ee8b8-2fb6-b041-fc5c-9821166cc79f@schultz.la> (raw)
In-Reply-To: <CAMteYTZHt8LOeBukf1ahZc1qyD7tbLU9oMD9n_=p43SzF6Oh9w@mail.gmail.com>

OK so I found the problem with proot. It's been fixed (very recently) upstream: https://github.com/proot-me/PRoot/pull/149 But as the discussion here: https://github.com/proot-me/PRoot/issues/127 reveals, they have some sticking points on making new releases, so the fix won't find its way downstream until those have been resolved.

I've applied the patches myself (using the work-around described below), and sure enough I can now use proot to build void packages as a non-privileged user under Docker.

If anyone thinks its worthwhile I can submit the patches as a pull request to void-linux, but otherwise probably just wait for things to work themselves out upstream.

Cheers, Jonathan

On 12/26/18 11:30 PM, Aleksey Tulinov wrote:
> I saw something similar before: https://github.com/Microsoft/WSL/issues/2981
> 
> Although it was WSL-related, user namespaces something something.
> 
> ср, 26 дек. 2018 г. в 08:34, Jonathan Schultz <jonathan@imatix.com>:
>>
>>Not sure whether to make a pull request with patches, or wait until a fixed version gets released upstream. Anyway it's documented for
>>>>> ERROR unshare (Operation not permitted)
>>>
>>> This is the actual error: unshare does not have setgid (or you are not
>>> in the group).
>>
>>
>> I believe the error is actually related to running xbps-src inside a Docker container, as setting setgid, or running as root make no difference. For the record, after much trial-and-error I have managed to find a combination that works. It required running the container as user root, and with both the --privileged and --cap-add=SYS_ADMIN options.
>>
>> However I have not entirely given up on finding a simpler solution. One promising route seemed to be to use the proot utility, which works in userspace, thus potentially avoiding all these permission problems. However when I try building using proot I see the following:
>>
>>> configure: creating ./config.status
>>> config.status: creating MakefileI the following:
>>> mv: cannot move './confT6XesZ/out' to 'Makefile': No such file or directory
>>> config.status: error: could not create Makefileerrors
>>
>> I've had a bit of a go at reverse engineering the xbps-src build process, but found it all a bit confusing, so wondering if anyone might have seen something like this before.
>>
>> Thanks as always.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "voidlinux" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
>> To post to this group, send email to voidlinux@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/CAN_yh5FT6-KeR4SDKT0%3DXU9%3DQoqaV18%3Dcr3ust0wsksVsKTtnQ%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To post to this group, send email to voidlinux@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/378ee8b8-2fb6-b041-fc5c-9821166cc79f%40schultz.la.
For more options, visit https://groups.google.com/d/optout.

      reply	other threads:[~2018-12-27 14:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-25  5:23 Jonathan Schultz
2018-12-25 14:05 ` Leah Neukirchen
2018-12-26  5:34   ` Jonathan Schultz
2018-12-26 15:30     ` Aleksey Tulinov
2018-12-27 14:40       ` Jonathan Schultz [this message]

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=378ee8b8-2fb6-b041-fc5c-9821166cc79f@schultz.la \
    --to=jonathan@schultz.la \
    --cc=aleksey.tulinov@gmail.com \
    --cc=jonathan@imatix.com \
    --cc=leah@vuxu.org \
    --cc=voidlinux@googlegroups.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;
as well as URLs for NNTP newsgroup(s).