I get the same issue. I've created systemd unit files for both mount and
automount:
$ cat /etc/systemd/system/share-apps.automount
[Unit]
Description=Automount Scratch
[Automount]
Where=/share/apps/
[Install]
WantedBy=multi-user.target
$ cat /etc/systemd/system/share-apps.mount
[Unit]
Descr
Aha - using usually Solaris zones, which have no such distinctions...
Anyway, in this case: yes, all our linux containers are privileged, which seems
to be the default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
You can run this to set a container to privileged mode:
lxc config set security.privileged true
And then restart it:
lxc restart
After that, the users inside the container are no longer mapped to a higher uid:
root 21301 0.0 0.0 602368 6120 ?Ss 17:45 0:00 [lxc monitor]
/va
See the last few comments of https://github.com/lxc/lxd/issues/2005
A privileged container is one where the container root user is the real
root. In an unprivileged one, root inside the container is just some
high-id random user on the host:
root 5393 0.0 0.0 530300 4964 ?Ss jun
Hmmm, not sure what "privileged container" means. Most machines are on xenial
now and use
lxc.aa_profile = lxc-container-default-cgns-with-mounting
if this is the question.
This way mounting manually as well as automatically via automount works,
but mounting something via the '-hosts' builtin ma
Is this a privileged container? Can you mount the NFS share manually
with the mount command?
** Changed in: autofs (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
