From: Lindsay Mathieson <lindsay.mathieson@gmail.com>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] unpriviliged lxc uid/gid mappings
Date: Mon, 19 Apr 2021 10:53:30 +1000 [thread overview]
Message-ID: <190926b5-0c91-b8d3-e653-5425103c0c0d@gmail.com> (raw)
I must say, I find the subject very confusing and difficult to parse. It
seems very difficult to setup with multiple user and container mappings
to maintain - I just setup 4 containers with 4 bind mounts each and
after a lot of fiddling, got them working, but I'm not confident on
maintenance for the future. I had to give up on the container that
needed access to 2 USB tuners and a Intel QuickSync GPU (vaapi), ended
up running that container privileged.
Is there any plans to simplify it for the future? I found the LXD (4.0?)
system of raw.idmap settings much easier to setup, I was able to
generically script that for containers.
Not complaining, I'm very happy with the overall setup I have at home -
PX Media Server and a PBS Server, much easier to maintain than my old
setup, and disaster recovery exists now :)
--
Lindsay
next reply other threads:[~2021-04-19 0:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 0:53 Lindsay Mathieson [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-19 0:52 Lindsay Mathieson
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=190926b5-0c91-b8d3-e653-5425103c0c0d@gmail.com \
--to=lindsay.mathieson@gmail.com \
--cc=pve-user@lists.proxmox.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