Example:

~$ LANG=C sudo whoami
sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
~$ LANG=C ls -l /usr/bin/sudo
-rwsr-xr-x 1 nobody nogroup 140944 Jan 14 07:41 /usr/bin/sudo
~$ LANG=C ls -l /var/lib/machines/builder/usr/bin/sudo
-rwsr-xr-x 1 root root 140944 Jan 14 07:41 
/var/lib/machines/builder/usr/bin/sudo


** Summary changed:

- Owner and group of few folders from Bind directory visible as nobody/nogroup 
within nspawn container 
+ Owner and group of few files and folders from Bind directory visible as 
nobody/nogroup within nspawn container

** Description changed:

- Owner and group of few folders from Bind directory visible as
+ Owner and group of few files and folders from Bind directory visible as
  nobody/nogroup when I check permission from within nspawn container.
  
  Create testing.nspawn:
  
  [Files]
  Bind=/patch/to/folder
- Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders in Bind directory inside container is the same as on 
host.
+ Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders and files in Bind directory inside container is the 
same as on host.
  
  Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
  Server 17.10 (systemd 233).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1688689

Title:
  Owner and group of few files and folders from Bind directory visible
  as nobody/nogroup within nspawn container

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  Owner and group of few files and folders from Bind directory visible
  as nobody/nogroup when I check permission from within nspawn
  container.

  Create testing.nspawn:

  [Files]
  Bind=/patch/to/folder
  Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders and files in Bind directory inside container is the 
same as on host.

  Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
  Server 17.10 (systemd 233).

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1688689/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to