[lxc-users] lxc container rootfs dev folder permission are changing from ro to rw inside container

Yasoda Padala padala.yasoda at gmail.com
Mon Feb 25 08:37:26 UTC 2019


yasoda at yasoda-HP-Z600-Workstation:~/.local/share/lxc/busybox$ lxc-attach -n
busybox
lxc-attach: busybox: utils.c: get_ns_uid: 548 No such file or directory -
Failed to open uid_map
lxc-attach: busybox: utils.c: get_ns_gid: 579 No such file or directory -
Failed to open gid_map

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.


*/ # mount cat /proc/mountsmount: mounting cat on /proc/mounts failed: No
such file or directory*
/ #
/ #

Please find attached container config

On Mon, Feb 25, 2019 at 2:01 PM Tomasz Chmielewski <tch at virtall.com> wrote:

> On 2019-02-25 17:27, Yasoda Padala wrote:
>
> > Actual results: dev folder of container rootfs is read-only on host
> > machine but inside container, it is writable.
> >
> > Please help with inputs on why the dev folder permissions are changed
> > on lxc-attach.
>
> Can you paste the output of:
>
> mount
> cat /proc/mounts
>
> from the container?
>
>
> Tomasz Chmielewski
> https://lxadm.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20190225/65209080/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: busybox-config
Type: application/octet-stream
Size: 1789 bytes
Desc: not available
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20190225/65209080/attachment-0001.obj>


More information about the lxc-users mailing list