-
Notifications
You must be signed in to change notification settings - Fork 18.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/dev/shm troubles in docker 1.4.1 #9820
Comments
in my env, It works like a charm.
please check ImagesID |
@xiaods you use Here's what
|
Turns out, this is somehow ubuntu-specific image issue:
|
I can reproduce this problem, but only with btrfs underneath the overlay driver. ext4 underneath overlay doesn't seem to have this problem. |
Yep, I'm seeing thins on btrfs too. I tried to link |
Yeah, overlay over btrfs working pretty bad :/ |
It's a known issue with overlay over btrfs, we need support for that in the On Sunday, December 28, 2014, Alexander Morozov notifications@github.com
|
@jfrazelle do you think it's possible to automatically output a warning if someone attempts to use overlay on top of btrfs (or other troublesome combinations), just as the "WARNING: No swap limit support"? |
+1 for @thaJeztah, warning could save a lot for time. If it's a know issue it should be disabled or at least visible. |
Ya I'll add a warning On Sunday, December 28, 2014, Ian Babrou notifications@github.com wrote:
|
@jfrazelle can we also add the underlying FS to |
@SvenDowideit there are potential contain many more underlying filesystem, Do we need support all filesystem? |
@xiaods we need to be able to get enough information from |
@SvenDowideit ok,let me collect overall fs. |
WARNING: I HAVE NO IDEA WHAT I'M DOING. Alright, maybe I know a little bit. I know that coreos uses btrfs, and that docker has officially disabled the overlay driver on btrfs: moby/moby#9820 That "fix" hasn't yet hit the stable coreos build, but on alpha, docker can't even start with this flag. In stable/beta, docker functions, but fails to start debian-based containers for some reason. If there's a particular reason that overlay is being used here, then the underlying FS needs to be ext4 (not totally sure what 'underlying' means here, but I'm going with it). But if not, we can just remove this flag and be done with it.
so, how will I fix this? |
Does this problem still exist? |
I'm locking the conversation on this issue, because the original issue reported here was resolved |
This doesn't work:
But this works:
cc @alexlarsson
The text was updated successfully, but these errors were encountered: