← Back to team overview

kernel-packages team mailing list archive

[Bug 1530617] Re: FUSE in wily image with upstart installed causes chaos


Thanks for looking into it. Are there any downsides to disabling udev in
the container (by removing /etc/init/udev.conf for example) if we don't
need the container to be notified of new devices?

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  FUSE in wily image with upstart installed causes chaos

Status in linux package in Ubuntu:
Status in lxc package in Ubuntu:
Status in upstart package in Ubuntu:

Bug description:

  lxc version: 1.1.4-0ubuntu1

  In a LXC container running Ubuntu 15.10, install upstart-sysv to
  replace systemd. Using FUSE then causes almost all processes in the
  container to be killed.

  The following steps reproduce the problem using sshfs:

  # create a wily container and attach to it
  sudo lxc-create -t download -n wily -- -d ubuntu -r wily -a amd64
  sudo lxc-start -n wily
  sudo lxc-attach -n wily

  # inside the container, install upstart-sysv and reboot
  apt-get update && apt-get -y install upstart-sysv

  # on the host, reattach to the container
  sudo lxc-attach -n wily

  # back in the container, install ssh and sshfs
  apt-get -y install openssh-server sshfs

  # create an ssh key pair in /root/.ssh

  # set up passwordless ssh
  mkdir ~ubuntu/.ssh
  cat /root/.ssh/id_rsa.pub >> ~ubuntu/.ssh/authorized_keys
  eval $(ssh-agent)
  ssh-add /root/.ssh/id_rsa

  # take a note of the running processes and their PIDs
  ps axjf

  # run sshfs
  mkdir /fuse
  sshfs ubuntu@localhost:/ /fuse

  # we are kicked out of the container
  # run ps again in the container
  sudo lxc-attach -n wily -- ps axjf

  # a whole bunch of processes are now gone. the getty processes now
  have new PIDs, indicating they have been restarted.

  Other debugging performed:
  - On a 14.10 host with lxc version 1.1.0~alpha2-0ubuntu3.3, the problem does not occur. FUSE works fine.
  - On the same 14.10 host with lxc upgraded to 1.1.5-0ubuntu3~ubuntu14.04.1, the problem occurs.
  - On a 15.10 host, when running a wily container without upstart, the problem does not occur.
  - On a 15.10 host, when running a trusty container, the problem does not occur.
  - The problem can't be reproduced outside a container (15.10 host, install upstart-sysv, then use FUSE)

To manage notifications about this bug go to:

Follow ups