-
Notifications
You must be signed in to change notification settings - Fork 1.3k
error creating overlay mount #1388
Comments
Oh this is bizarre -- my host daemon is 18.09.4 and it works fine there, but I can indeed reproduce in boot2docker (and they're both overlay2). I wonder if there's something in boot2docker's kernel that we need to tweak? Here's the last few lines of
|
https://github.com/docker/docker.github.io/blob/b7b1e03f0423c6cbc50ac3e242407be14988ebc6/storage/storagedriver/overlayfs-driver.md#how-the-overlay2-driver-works implies we still have a layer limit, but it's much higher than 100 (and moby/moby#26380 talks about getting up to 122 reliably), so I'm not 100% sure what's happening here. |
Nothing in v18.09.0...v18.09.1 jumps out as particularly interesting, so maybe there's something in the kernel between 4.14.79 and 4.14.92 that can help explain what's changed? |
Crap, definitely not the kernel -- just tried doing a build of master on 4.14.79 and it still stops at Step 62. Trying dropping the Docker version back down now. |
Welp, that works fine, so it's narrowed down to being caused by something in docker-archive/docker-ce@v18.09.0...v18.09.1 🤔 |
Looks like docker-archive/engine#84 / moby/moby#37993 is probably the most likely candidate (especially since the error message in moby/moby#37970 appears to match the one we're getting exactly). What I'm still fuzzy on is why this would be causing the error to show up when the PR is literally supposed to be the fix for it. 😕 cc @thaJeztah (Also not sure why boot2docker is hitting it but my host isn't -- the value of |
Ran https://github.com/moby/moby/blob/2bfa24b39393f3e6e1ec38e1d76004e5a50d109f/contrib/check-config.sh against our current kernel config (for giggles, just in case) and it shows appropriately that we're only missing |
We are kind of blocked by this. Any leads I can follow to diagnose and try to fix this issue? |
Dockerfile.txt
Result for most recent released versions.
When build Docker images with more than 50-plus layers, the build will fail exactly at step 62 as shown below.
To reproduce the bug.
The text was updated successfully, but these errors were encountered: