all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Audio/sound (ALSA) in guix environment --container
Date: Wed, 27 Mar 2019 11:38:07 +0100	[thread overview]
Message-ID: <8736n84n74.fsf@elephly.net> (raw)
In-Reply-To: <87d0mcpqy7.fsf@ambrevar.xyz>


Pierre Neidhardt <mail@ambrevar.xyz> writes:

> I've just "guix pull"ed and I get the following:
>
> --8<---------------cut here---------------start------------->8---
>> guix environment --container --ad-hoc coreutils shadow 
> # id
> uid=0(ambrevar) gid=0(users) groups=0(users),65534(overflow)
> # groupadd audio
> groupadd: PAM: Critical error - immediate abort
> # useradd foo
> useradd: PAM: Critical error - immediate abort
> --8<---------------cut here---------------end--------------->8---
>
> Any idea where to go from here?

I suppose /etc/pam.d/ also needs to be in the container.

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> I agree.  Defaulting to UID 0 is not good.  (“conda” is an example of
>> one application that has very different behaviour when it thinks it is
>> running as root.)
>
> What about defaulting to 1000?  It's rather common, so I guess that
> would be anonymous enough and "just work".

Would it make sense to map the current user’s UID into the container
instead of using a fixed UID?

-- 
Ricardo

  reply	other threads:[~2019-03-27 10:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 19:50 Audio/sound (ALSA) in guix environment --container Pierre Neidhardt
2019-03-26 17:15 ` Ludovic Courtès
2019-03-26 17:21   ` Ricardo Wurmus
2019-03-27 10:11     ` Pierre Neidhardt
2019-03-27 10:38       ` Ricardo Wurmus [this message]
2019-03-27 11:05         ` Pierre Neidhardt
2019-03-27 11:10           ` Ricardo Wurmus
2019-03-27 15:03             ` Ludovic Courtès
2019-03-27 15:14               ` Ricardo Wurmus
2019-04-02 16:17                 ` Ludovic Courtès
2019-04-03  8:01                   ` Pierre Neidhardt
2019-03-27 11:14         ` Ludovic Courtès

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=8736n84n74.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.