What `native overlay diff` mean in overlay2 storage driver?

This seems to be related to the OVERLAY_FS_REDIRECT_DIR kernel option, which is described in Kconfig as:

config OVERLAY_FS_REDIRECT_DIR
bool "Overlayfs: turn on redirect dir feature by default"
depends on OVERLAY_FS
help

If this config option is enabled then overlay filesystems will use redirects when renaming directories by default. In this case it is still possible to turn off redirects globally with the "redirect_dir=off" module option or on a filesystem instance basis with the "redirect_dir=off" mount option.

Note, that redirects are not backward compatible. That is, mounting an overlay which has redirects on a kernel that doesn't support this feature will have unexpected results.

If unsure, say N.

Some discussion on moby issues 34342 and 34320 indicates that, if all of the following are true:

1. the OVERLAY_FS_REDIRECT_DIR kernel option is enabled
2. the storage engine is overlay2 (the default in most cases)
3. docker is storing images on a file system that is not mounted with redirect_dir=off
4. the "native" diff driver is used

5. a nonempty directory is renamed as part of a docker build, e.g. in a Dockerfile like the following:

   FROM busybox
   
   RUN mkdir /dir1
   RUN touch /dir1/newfile
   RUN mv /dir1 /dir2
   

Then the resulting image will not properly record the contents of the renamed directory (i.e., dir2 will not contain newfile) because the directory rename was implemented as a redirect using an extended file attribute (xattr) which is not understood by the docker archiving process. To solve this problem, when the first three conditions above are met, then docker will use the "naive" diff driver which produces correct images, but is slower than the "native" diff driver.

It seems like it is safe to ignore the warning, but if you notice slow builds, then you could try remounting the volume serving /var/lib/docker with the option redirect_dir=off.