linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Axtens <dja@axtens.net>
To: vgoyal@redhat.com, linux-fsdevel@vger.kernel.org,
	linux-unionfs@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: mpe@ellerman.id.au, mszeredi@redhat.com, dchinner@redhat.com
Subject: 45aebeaf4f67 "ovl: Ensure upper filesystem supports d_type" breaking Docker
Date: Mon, 16 May 2016 16:45:09 +1000	[thread overview]
Message-ID: <87d1ombix6.fsf@gamma.ozlabs.ibm.com> (raw)

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

             reply	other threads:[~2016-05-16  6:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16  6:45 Daniel Axtens [this message]
2016-05-16 13:07 ` 45aebeaf4f67 "ovl: Ensure upper filesystem supports d_type" breaking Docker Vivek Goyal
2016-05-17  6:28   ` Al Viro
2016-05-17  8:15     ` Miklos Szeredi
2016-05-17 12:10       ` Vivek Goyal
2016-05-17 14:24         ` Miklos Szeredi
2016-05-18  3:33         ` Daniel Axtens
2016-05-17 22:39   ` Daniel Axtens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d1ombix6.fsf@gamma.ozlabs.ibm.com \
    --to=dja@axtens.net \
    --cc=dchinner@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=mszeredi@redhat.com \
    --cc=vgoyal@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).