On 1 January 2015 at 11:55, Joey Hess <i...@joeyh.name> wrote: > This is pretty horrible! Note that only docker exec behaves this way; > docker run and docker attach operate with the filesystem correctly chrooted > to the container.
I agree that this is horrible, but the docker.io package description does state: > Also, note that kernel version 3.8 or above is required for proper operation > of the daemon process, and that any lower versions may have subtle and/or > glaring issues. I really wish https://github.com/docker/docker/pull/7681 had merged upstream instead of being closed. There's some further discussion about this happening upstream in https://github.com/docker/docker/issues/8969 now, but it's essentially stalled. I would actually be very surprised if the issues you've encountered so far are the only issues with Docker on a 3.2 kernel. The fact is that Docker is completely 100% unsupported on kernels lower than 3.8, but to my knowledge, the sentence in the description is the best we can do to make this known/clear. If there are better ways we could highlight this in the packaging, especially warning users that there are serious issues with older kernels (even if they seem to mostly work, as you've discovered), I'm definitely very interested in hearing them and I'm sure Paul is too (or maybe he already has more ideas he just hasn't shared with me). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
