lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <87d1ombix6.fsf@gamma.ozlabs.ibm.com> Date: Mon, 16 May 2016 16:45:09 +1000 From: Daniel Axtens <dja@...ens.net> To: vgoyal@...hat.com, linux-fsdevel@...r.kernel.org, linux-unionfs@...r.kernel.org, linux-kernel@...r.kernel.org Cc: mpe@...erman.id.au, mszeredi@...hat.com, dchinner@...hat.com Subject: 45aebeaf4f67 "ovl: Ensure upper filesystem supports d_type" breaking Docker Hi, I installed a fresh 4.6.0 kernel on my ppc64le system, and tried to run a docker container. It failed. Docker gave me errors like this: docker: Error response from daemon: error creating overlay mount to /var/lib/docker/overlay/2bc07cedad2770da2f384d5c1e81a6f45fa3c44a7658f10d02e5973ef76620fc-init/merged: invalid argument. In dmesg, I'm seeing: overlayfs: upper fs needs to support d_type. Reverting 45aebeaf4f67 ("ovl: Ensure upper filesystem supports d_type") fixes the issue for me. I haven't investigated the root cause yet - at a guess I'd say either Docker's layering system, or some weird interaction with namespacing, maybe? I'll have a look when I get a spare moment. For reference, I'm using docker 1.11.0-dev. Regards, Daniel Axtens
Powered by blists - more mailing lists