Arch Linux

Please read this before reporting a bug:

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#63252 - kernel 5.2: regression in overlayfs causes snap and docker to fail

Attached to Project: Arch Linux
Opened by Ludovic Fauvet (etix) - Monday, 22 July 2019, 10:33 GMT
Last edited by freswa (frederik) - Saturday, 22 February 2020, 21:21 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No


Description: A regression in overlayfs makes application like snap and docker to fail

Additional info:
* Kernel patch:
* Issue on docker/moby:

Steps to reproduce:
* use kernel 5.2
* build a docker image
* the build fails with warnings about upper/work dir

The fix was apparently not yet merged in 5.2.2, applying the aforementioned patch should solve the issue until the final fix is pulled into the official kernel tree.

This task depends upon

Closed by  freswa (frederik)
Saturday, 22 February 2020, 21:21 GMT
Reason for closing:  Fixed
Additional comments about closing:  5.3.1
Comment by Ludovic Fauvet (etix) - Monday, 22 July 2019, 10:39 GMT
I forgot to mention that the patch was pulled in overlayfs-next and linux-next already.
Comment by Ludovic Fauvet (etix) - Tuesday, 30 July 2019, 09:19 GMT Comment by Ludovic Fauvet (etix) - Wednesday, 04 September 2019, 07:57 GMT Comment by Julio (The_Loko) - Wednesday, 11 September 2019, 16:29 GMT
  • Field changed: Percent Complete (100% → 0%)
It still happens with linux 5.2.13.arch1-1 and docker 1:19.03.2-1
Comment by loqs (loqs) - Wednesday, 11 September 2019, 18:05 GMT
Has anyone contacted the kernel developers to find out why the commit is not in 5.3?
Comment by Ludovic Fauvet (etix) - Wednesday, 11 September 2019, 18:08 GMT
Actually, the problem is not on the kernel side. The kernel just enforced a check for an undefined behavior.
Comment by loqs (loqs) - Wednesday, 11 September 2019, 19:05 GMT
@etix do you have a less nasty fix for the docker PKGBUILD until there is a release containing 477bf1e413708076f9ed8cd316102765cc5bdb11 ?
PKGBUILD2.diff switch to patch from git cherry-pick
PKGBUILD3.diff use ce5b02683e83ec9aa89927a9ce5d276787cc8823 [1]
PKGBUILD includes changes from PKGBUILD3.diff
@etix does the attached PKGBUILD resolve the issue for you?

Comment by Ludovic Fauvet (etix) - Thursday, 12 September 2019, 09:08 GMT
@loqs Absolutely the PKGBUILD including the PKGBUILD3.diff seems to fix the issue for me.
Comment by loqs (loqs) - Thursday, 19 September 2019, 20:37 GMT