Picked up and categorized subjectively. Comments and pull requests are welcome.
Issue | Abstract | Impact | Reproducibility | Cause | Solution | Notes |
---|---|---|---|---|---|---|
β #783 | Cannot access to a directory due to a permission error | π Medium | π Easy | Expected AUFS behavior. dirperm1 mount option fixes this issue. |
Update the kernel (AUFS >= 2008xxxx?) and Docker daemon (>= 1.7) | Confirm: `docker info |
β #18180 | A process becomes a zombie and hangs up | π± High | π± Hard(multiprocessor) π Easy(uniprocessor) |
Compatibility between the kernel and AUFS | Update the kernel (AUFS >= 20160111) | Especially Java apps and MongoDB are affected |
β¬ #20199 | fcntl(F_SETFL, O_APPEND) is ignored and hence data can be corrupted |
π± High | π Easy | AUFS bug | None (Workaround: patch) | Especially Dovecot is affected |
β¬ #20240 | Weird permission even though dirperm1 is enabled |
π Medium | π± Hard | Unanalyzed | None |
Non-bug issues:
- AUFS is not available in the mainline kernelοΌOnly a few distros (Ubuntu, Boot2Docker, ..) support AUFS, but even for Ubuntu, Canonical says "AUFS will disappear".
Issue | Abstract | Impact | Reproducibility | Cause | Solution | Notes |
---|---|---|---|---|---|---|
β¬ #10180 | File corruption | π± High | π± Hard | Unanalyzed | None | Especially RPMs are affected |
β¬ #12080 | Cannot use UNIX domain sockets | π Medium | π Easy | Overlay Bug | None (Workaround: patch) | |
β¬ #19082 | Weird behavior after removing the current directory | π Low | π Easy | Overlay Bug | None (Workaround: patch) | |
β¬ #19647 | Untar fails intermittently | π± High | π± Hard | Unanalyzed (Overlay bug related to symbolic links?) | None | |
β¬ #19758 | Daemon hangs up after frequent docker run |
π± High | π± Hard | Unanalyzed (Overlay bug related to the number of processors?) | None |
Non-bug issues:
- π± High inode usage
- Red Hat says OverlayFS is Tech Preview
Issue | Abstract | Impact | Reproducibility | Cause | Solution | Notes |
---|---|---|---|---|---|---|
β #19073 | sendfile(2) can be unkillable |
π Low | π Easy | BtrFS bug | None | Not likely to happen in production, but needs consideration for public PaaS |
β¬ #20080 | cgroups kmem limit leads crash and data corruption | π± High | π Easy? | Btrfs bug | Avoid kmem limit configuration? |
Non-bug issues:
- Slow #10161
- No page sharing (e.g. same DLLs are loaded redundantly) http://comments.gmane.org/gmane.comp.sysutils.docker.devel/1384
- Docker says BtrFS is Experimental. Red Hat says BtrFS is Tech Preview.
Issue | Abstract | Impact | Reproducibility | Cause | Solution | Notes |
---|---|---|---|---|---|---|
β #20153 | Some operations fail due to EBUSY |
π Medium | π Medium | Daemon bug | Update Docker daemon |
Non-bug issues:
- Docker says ZFS is not recommended for production.
Issue | Abstract | Impact | Reproducibility | Cause | Solution | Notes |
---|---|---|---|---|---|---|
β #4036 | Mount fails | π± High | π Easy | udev sync disabled | Use a Docker daemon binary which supports udev sync | Confirm: `docker info |
β¬ #5684 | Cannot restart containers after restaring the daemon | π± High | π Easy | Unanalyzed | None | |
β¬ #20401 | Infinite βmount/remountβ loop, which makes the system unresponsive | π± High | π± High | Unanalyzed (perhaps related to XFS) | None |
Non-bug issues:
- Slow #10161
- No page sharing (e.g. same DLLs are loaded redundantly) http://comments.gmane.org/gmane.comp.sysutils.docker.devel/1384
It totally depends on your workload, but Docker, Inc. says AUFS and Devicemapper (direct-lvm) are "production-ready".
Although not listed in the above table, VFS driver is also attractive for its robustness.
Links:
- https://jpetazzo.github.io/assets/2015-03-03-not-so-deep-dive-into-docker-storage-drivers.html#1
- http://www.projectatomic.io/docs/filesystems/
You know, containers should be "immutable" and "disposable".
For persistent data and some special temporary data, you should better consider using an external volume (docker run -v
).
Links:
Issue | Abstract | Impact | Reproducibility | Cause | Solution | Notes |
---|---|---|---|---|---|---|
β¬ #18776 | TCP checksums are ignored | π± High | π± Hard | Kernel bug | Update the kernel | blog |