On 11/27/2015 7:42 AM, Neil Davies wrote: > Hi > > I’ve been successfully running containers for several years. > initially using lxc and now docker, inside machines where there was: > an outer AFS service; > accessed by the processes inside the container. > > It worked fine (we are happy with the UID/token issue) until a recent > upgrade. > After this upgrade I am no longer able, in the container, able to push tokens > into the kernel - it gives a pioctl. > > That was a couple of weeks ago it broke, I backed out the change and I’m > going to try to isolate the issue - before I do I was wondering if there was > anyone else on the list that has had this experience? > > Neil
I have been working with the Docker Container engine on Windows Server 2016 TP4. Access to AFS simply does not work there because non-standard device drivers (kernel modules) are not permitted to be accessed from within the Container. This decision was made to improve the portability of Container images. It would not surprise me in the least if the same restrictions are added to Containers on Linux to improve portability of Containers on Linux as well. Jeffrey Altman
<<attachment: jaltman.vcf>>
smime.p7s
Description: S/MIME Cryptographic Signature
