Your message dated Sun, 10 Apr 2016 18:25:56 +0200
with message-id <[email protected]>
and subject line Re: Bug#770684: lxc-start creates /dev with wrong permissions 
if invoked with restrictive umask
has caused the Debian Bug report #770684,
regarding lxc-start creates /dev with wrong permissions if invoked with 
restrictive umask
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
770684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770684
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lxc
Version: 1:1.0.6-3
Severity: minor

Recently I started a container via « sudo lxc-start … » without
configuring sudo to reset the umask first.  I subsequently found
SSHing into the container was slightly broken and user sessions were
hanging in weird ways.  This turned out to be because /dev had been
created with mode 0750 instead of the proper 0755; the problem went
away when I explicitly reset the umask from 0027 to 0022.  It would be
nice if LXC programs that deal with files in the container either
reset the umask themselves or explicitly chmodded created files to
avoid causing problems when so invoked.

   ---> Drake Wilson

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lxc depends on:
ii  init-system-helpers  1.21
ii  libapparmor1         2.9.0-2
ii  libc6                2.19-13
ii  libcap2              1:2.24-6
ii  libseccomp2          2.1.1-1
ii  libselinux1          2.3-2
ii  multiarch-support    2.19-13
ii  python3              3.4.2-1

Versions of packages lxc recommends:
ii  debootstrap  1.0.64
ii  openssl      1.0.1j-1
ii  rsync        3.1.1-2+b1

Versions of packages lxc suggests:
pn  lua5.2  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1:1.1.5-1

Hi Ivan,

On Sun, Apr 10, 2016 at 06:22:13PM +0200, Ivan Vilata i Balaguer wrote:
> Evgeni Golov (2016-03-26 11:21:00 +0100) wrote:
> 
> > control: tags -1 + moreinfo
> > 
> > On Wed, Jul 22, 2015 at 01:33:22PM +0200, Ivan Vilata i Balaguer wrote:
> > > I can confirm that this still happens with version ``1:1.0.7-3``, only 
> > > with
> > > containers with ``lxc.autodev=1`` where ``/dev`` is a temporary file 
> > > system
> > > for ``udev``.  Otherwise the permission of the physical directory is kept.
> > 
> > Can you retry with 1:1.1.5-1 as in Stretch and Sid please?
> > I cannot reproduce the issue there anymore.
> 
> Neither can I, with 1:1.1.5-1 and the configuration I indicated above,
> ``/dev`` gets mode 0755 and things work ok now when creating the
> container with umask 0027.

Perfect, thanks!
Marking as fixed then.

Greets
Evgeni

--- End Message ---

Reply via email to