You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@tklauser requested issue #40893 to be considered for backport to the next 1.15 minor release.
@gopherbot please consider backporting this to 1.15.
The use of copy_file_range is new in 1.15 and this causes failures doing file system operations in containers running on older kernels which do not provide the copy_file_range syscall.
The text was updated successfully, but these errors were encountered:
* src/copy.c (sparse_copy): Upon EPERM from copy_file_range(),
fall back to a standard copy, which will give a more accurate
error as to whether the issue is with the source or destination.
Also this will avoid the issue where seccomp or apparmor are
not configured to handle copy_file_range(), in which case
the fall back standard copy would succeed without issue.
This specific issue with seccomp was noticed for example in:
golang/go#40900
@tklauser requested issue #40893 to be considered for backport to the next 1.15 minor release.
The text was updated successfully, but these errors were encountered: