kernel-packages team mailing list archive

[Serge Hallyn <1214500@xxxxxxxxxxxxxxxxxx>]

Regarding creating the socket as a non-root user - did you chown the
directory to your user's uid?  I have no problem once I've done that in
running the server.

I have the same issue with the client:

sudo mkdir /mnt2 /upper
sudo mount -t overlayfs -o lowerdir=/mnt2,upperdir=/upper none /mnt
sudo chown -R ubuntu: /mnt
./serv.py /mnt/sock &
./client.py /mnt/sock

Traceback (most recent call last):
  File "./client.py", line 7, in <module>
    s.connect(socketname)
  File "/usr/lib/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)
socket.error: [Errno 111] Connection refused

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1214500

Title:
  consistent failure with overlayfs and unix sockets

Status in “linux” package in Ubuntu:
  Incomplete
Status in “lxc” package in Ubuntu:
  New

Bug description:
  Seems like overlayfs and unix sockets are not playing well. It might
  be racy, as it fails consistently on my laptop with an SSD, whereas
  for smoser it only failed a single time.

  Steps to reproduce:

  REL="precise"
  $ sudo lxc-create -n source-$REL-amd64 -t ubuntu-cloud -- \
     --release=$REL --arch=amd64

  ## clone via overlayfs ##
  $ sudo lxc-clone --snapshot -B overlayfs -o source-$REL-amd64 -n $REL-overlayfs-01

  $ sudo lxc-start -n $REL-overlayfs-01

  
  ### inside ###
  $ sudo apt-get update && sudo apt-get install supervisor -y

  $ sudo service supervisor stop
  $ sudo sed -i.dist 's,var/run/*supervisor.sock,srv/supervisor.sock,' /etc/supervisor/supervisord.conf
  $ sudo service supervisor start
  $ sudo supervisorctl maintail
  unix:///srv/supervisor.sock refused connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214500/+subscriptions