Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#56050 - [docker] Prevent overlay2 mount errors in combination with 4.13 kernel
Attached to Project:
Community Packages
Opened by Markus Doits (doits) - Thursday, 19 October 2017, 17:12 GMT
Last edited by Sébastien Luttringer (seblu) - Friday, 29 December 2017, 12:47 GMT
Opened by Markus Doits (doits) - Thursday, 19 October 2017, 17:12 GMT
Last edited by Sébastien Luttringer (seblu) - Friday, 29 December 2017, 12:47 GMT
|
DetailsDescription:
There is a bug in current docker versions (currently 1:17.10.0-1) that sometimes this errors happens: error creating overlay mount to /var/lib/docker/overlay2/ID/merged: device or resource busy As per https://github.com/moby/moby/issues/34672 this is a bug triggered by the 4.13 kernel which was silently ignored before (read bug report for more information). There is a patch available which seems to address the issue (verified by me by running multiple docker images without an error): https://github.com/moby/moby/pull/34948 Until it is merged or the kernel regression is fixed, it might be a good idea to implement this patch by ourselves in arch to fix the nasty error. I simply downloaded the patch (https://patch-diff.githubusercontent.com/raw/moby/moby/pull/34948.diff) and updated the PKGBUILD: prepare() { pushd $srcdir/docker-ce/components/engine/ patch -Np1 -i "${srcdir}/../34948.diff" popd } This can be removed when either https://github.com/moby/moby/pull/34948 is merged or upstream kernel is fixed. |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Friday, 29 December 2017, 12:47 GMT
Reason for closing: Upstream
Additional comments about closing: 17.12
Friday, 29 December 2017, 12:47 GMT
Reason for closing: Upstream
Additional comments about closing: 17.12
17.11 does not have this patch applied (https://github.com/docker/docker-ce/blob/17.11/components/engine/daemon/graphdriver/overlay2/overlay.go), but 17.12 has it looks like (https://github.com/docker/docker-ce/blob/17.12/components/engine/daemon/graphdriver/overlay2/overlay.go)