Support f2fs filesystem

[tomaszduda23]

There is effort to run docker on Android opencontainers/runc#4443. It is possible to run also k3s. Without this k3s will exit with following error

E1012 16:21:00.216260    7851 kubelet.go:1431] "Failed to start ContainerManager" err="failed to get rootfs info: failed to get mount point for device \"/dev/block/dm-53\": no partition info for device \"/dev/block/dm-53\""

Android uses following options to mount /data.

/dev/block/dm-53 on /data type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,active_logs=6,reserve_root=32768,resuid=0,resgid=1065,noatgc,inlinecrypt,alloc_mode=default,fsync_mode=nobarrier)

which is ignored during look up.

Testing requires:

1. patching kernel
2. adding this patch
3. patching Support cgroup on Android opencontainers/runc#4443
4. k3s can run in agent mode

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[SergeyKanzhelev]

please provide some description to the PR including how this is validated

[tomaszduda23]

@SergeyKanzhelev do you think that we could get it merged? It is needed to run k3s on android.
You can find more details in this thread k3s-io/k3s#11028 (reply in thread)

[tomaszduda23]

@iwankgb would you mind to look on this? How could I get this merged? It allows to use k3s on Android (it is not main stream thing but why not). I already got runc fix merge opencontainers/runc#4513. If this could be merged official k3s build would work on Android (with custom kernel). Than I would like to add package to termux. You can find some details at k3s-io/k3s#11028

[github-actions]

This PR is stale because it has been open 90 days with no activity. This PR will be closed in 30 days unless new comments are made or the stale label is removed. To skip these checks, apply the "lifecycle/frozen" label.