On Mon, Apr 18, 2016 at 02:14:58PM -0400, Barry Warsaw wrote: > With today's dist-upgrade, I am unable to enter an existing or newly > created chroot, nor am I able to sbuild or adt-run with the chroot. > > I had an existing sid-amd64 chroot which I could not enter. I then > removed the chroot and recreated it with mk-sbuild. Now I get: > > % schroot -u root -c sid-amd64 > E: 15binfmt: update-binfmts: unable to open > /var/run/schroot/mount/sid-amd64-98db94f4-3bc6-4948-95a6-57a8e986bba9/bin/sh: > Operation not permitted > E: 20copyfiles: cp: cannot create regular file > '/var/run/schroot/mount/sid-amd64-98db94f4-3bc6-4948-95a6-57a8e986bba9/etc/resolv.conf': > Operation not permitted > E: 15binfmt: update-binfmts: unable to open > /var/run/schroot/mount/sid-amd64-98db94f4-3bc6-4948-95a6-57a8e986bba9/bin/sh: > Operation not permitted > E: sid-amd64-98db94f4-3bc6-4948-95a6-57a8e986bba9: Chroot setup > failed: stage=setup-start
I've been seeing something similar. Am I right to assume that these are union-type=overlay? If so, this seems to be a change in the kernel. Running linux-image-4.5.0-1-amd64, I see various failures using overlay but rebooting into linux-image-4.4.0-1-amd64 I am again able to use schroot/sbuild. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <james...@debian.org>
