touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #126782
[Bug 1530617] Re: FUSE in wily image with upstart installed causes chaos
ubuntu@upstart:~$ sudo lxc-start -n cloud1; sudo lxc-attach -n cloud1
root@cloud1:~# ps -ef
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 04:55 ? 00:00:00 /sbin/init
root 99 0 0 04:55 pts/0 00:00:00 /bin/bash
root 117 1 0 04:55 ? 00:00:00 @sbin/plymouthd --mode=boot --attach-to-session
root 118 1 0 04:55 ? 00:00:00 plymouth-upstart-bridge
root 123 1 0 04:55 ? 00:00:00 mountall --daemon
root 127 1 0 04:55 ? 00:00:00 /bin/sh -e /proc/self/fd/9
root 136 127 0 04:55 ? 00:00:00 /bin/sh - /sbin/MAKEDEV std fd ppp tun
root 170 1 0 04:55 ? 00:00:00 run-parts --lsbsysinit /etc/update-motd.d
root 210 170 0 04:55 ? 00:00:00 /bin/sh -e /usr/lib/update-notifier/update-motd-updates-available
root 325 210 0 04:55 ? 00:00:00 /usr/bin/python3 /usr/lib/update-notifier/apt-check --human-readable
root 391 1 0 04:55 ? 00:00:00 upstart-udev-bridge --daemon
root 401 1 0 04:55 ? 00:00:00 /lib/systemd/systemd-udevd --daemon
root 453 1 0 04:55 ? 00:00:00 upstart-socket-bridge --daemon
root 998 1 0 04:55 ? 00:00:00 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0
syslog 1537 1 0 04:55 ? 00:00:00 rsyslogd
root 1554 1 0 04:55 ? 00:00:00 /usr/bin/python3 /usr/bin/cloud-init modules --mode=config
root 1555 1 0 04:55 ? 00:00:00 [sh] <defunct>
root 1574 1 0 04:55 ? 00:00:00 /sbin/cgproxy --sigstop
root 1627 1 0 04:55 ? 00:00:00 upstart-file-bridge --daemon
message+ 1678 1 0 04:55 ? 00:00:00 dbus-daemon --system --fork
root 2014 1554 0 04:55 ? 00:00:00 initctl version
root 2016 1 0 04:55 ? 00:00:00 /bin/sh -e /proc/self/fd/9
root 2018 1 0 04:55 lxc/tty4 00:00:00 /sbin/getty -8 38400 tty4
root 2020 1 0 04:55 ? 00:00:00 /bin/sh -e /proc/self/fd/9
root 2024 1 0 04:55 ? 00:00:00 /bin/sh -e /proc/self/fd/9
root 2026 1 0 04:55 ? 00:00:00 atd
root 2029 1 0 04:55 ? 00:00:00 cron
root 2031 1 0 04:55 ? 00:00:00 acpid -c /etc/acpi/events -s /var/run/acpid.socket
root 2033 1 0 04:55 lxc/tty2 00:00:00 /sbin/getty -8 38400 tty2
root 2035 99 0 04:55 pts/0 00:00:00 ps -ef
root 2036 1 0 04:55 lxc/tty3 00:00:00 /sbin/getty -8 38400 tty3
root@cloud1:~# ubuntu@upstart:~$
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1530617
Title:
FUSE in wily image with upstart installed causes chaos
Status in lxc package in Ubuntu:
Confirmed
Status in upstart package in Ubuntu:
New
Bug description:
Host:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu 15.10"
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
reboot
# 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
ssh-keygen
# 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:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1530617/+subscriptions
References