From: Edouard Klein <edou@rdklein.fr>
To: help-guix@gnu.org
Subject: Systemd guix containers: unable to execute Permission denied
Date: Sat, 19 Jun 2021 16:20:47 +0200 [thread overview]
Message-ID: <8735te9br4.fsf@rdklein.fr> (raw)
Hi,
I'm running a container using a systemd unit. This unit calls a script
that call guix system container and calls the returned script.
When I launch this script by itself, everything works as expected.
When I launch this script with systemd, I can launch any command except
as root in the container.
For example, once I get a shell in the container with guix container
exec, I can do:
sudo -u nginx echo toto
And it will succeed when the container is launched by hand, but failed
when launched with systemd.
Any idea, even far fetched, will be appreciated. I have a burning hatred
for systemd (not my choice) that this incident is fueling.
I've tried everything I could think of:
- activating and deactivating various systemd flags
- changing the uid of nginx to match a user on the host system
- changing the uid of nginx to avoid matching a user on the host system
- stopping nscd on the container,
etc.
I'm looking into other means of achieving what I want, but this SHOULD
work, and it WOULD if it wasn't for effing systemd.
Cheers,
Edouard.
reply other threads:[~2021-06-19 14:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735te9br4.fsf@rdklein.fr \
--to=edou@rdklein.fr \
--cc=help-guix@gnu.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).