Bug#847154: linux-image-amd64: Disabling vsyscall interface may break docker run

2016-12-17 Thread Ben Hutchings
Control: reassign -1 src:linux 4.8.4-1~exp1 Control: tag -1 pending This change also broke the version of dietlibc in stable, and even some packages in unstable. (dietlibc is statically linked, and they had not been rebuilt since dietlibc stopped using vsyscalls.) As quite a few packages are aff

Bug#847154: linux-image-amd64: Disabling vsyscall interface may break docker run

2016-12-06 Thread Olaf Meeuwissen
Ian Campbell writes: > On Tue, 2016-12-06 at 14:17 +, Ben Hutchings wrote: >> >> But perhas we should more explicit in this message, e.g.: >> >> "This breaks (e)glibc 2.13 and earlier, which may still be installed in >> a chroot or container environment based on Debian 7, RHEL/CentOS 6 or >

Bug#847154: linux-image-amd64: Disabling vsyscall interface may break docker run

2016-12-06 Thread Ian Campbell
On Tue, 2016-12-06 at 14:17 +, Ben Hutchings wrote: > > But perhas we should more explicit in this message, e.g.: > > "This breaks (e)glibc 2.13 and earlier, which may still be installed in > a chroot or container environment based on Debian 7, RHEL/CentOS 6 or > earlier versions." That's a

Bug#847154: linux-image-amd64: Disabling vsyscall interface may break docker run

2016-12-06 Thread Ben Hutchings
On Tue, 2016-12-06 at 10:02 +, Ian Campbell wrote: > On Tue, 2016-12-06 at 12:56 +0900, Olaf Meeuwissen wrote: > > You may want to add to the NEWS blurb that disabling the old 'virtual > > syscall' interface can lead to crashes when trying to run a Docker > > container.  With upstream's docker-

Bug#847154: linux-image-amd64: Disabling vsyscall interface may break docker run

2016-12-05 Thread Olaf Meeuwissen
Package: linux-image-amd64 Version: 4.8+76 Severity: wishlist Dear Maintainer, You may want to add to the NEWS blurb that disabling the old 'virtual syscall' interface can lead to crashes when trying to run a Docker container. With upstream's docker-engine-1.12.3-0~stretch, I see docker run -