Bug:sysbox-deploy-k8s:v0.6.1: Getting errors after kernel upgrade.

My worker node is deploying correctly on an Ubuntu 20.04 with a 5.4.0 kernel. My setup requires a kernel with acs_override patch. Whenever I use any different kernel other than the original mainline 5.4.0, I get a BackOff container restarting error. This is the log from sysbox-deploy-k8s:

E0728 21:43:13.399000 26 memcache.go:255] couldn't get resource list for custom.metrics.k8s.io/v1beta1: Got empty response for: custom.metrics.k8s.io/v1beta1
E0728 21:43:13.621834 88 memcache.go:255] couldn't get resource list for custom.metrics.k8s.io/v1beta1: Got empty response for: custom.metrics.k8s.io/v1beta1
Detected Kubernetes version v1.23
Adding K8s taint "sysbox-runtime=not-running:NoSchedule" to node ...
E0728 21:43:13.785878 131 memcache.go:255] couldn't get resource list for custom.metrics.k8s.io/v1beta1: Got empty response for: custom.metrics.k8s.io/v1beta1
node/node-X-X-XX-XX-XX.example.com modified
Adding K8s label "sysbox-runtime=installing" to node ...
E0728 21:43:14.016878 159 memcache.go:255] couldn't get resource list for custom.metrics.k8s.io/v1beta1: Got empty response for: custom.metrics.k8s.io/v1beta1
node/node-X-X-XX-XX-XX.example.com not labeled
Installing Sysbox dependencies on host ...
Copying shiftfs sources to host ...
Kernel version 5.4 is >= 5.4 and < 5.8
Deploying Sysbox installer helper on the host ...
Running Sysbox installer helper on the host (may take several seconds) ...
Stopping the Sysbox installer helper on the host ...
Removing Sysbox installer helper from the host ...
Installing Sysbox on host ...
Configuring host sysctls ...
sysctl: cannot stat /proc/sys/kernel/unprivileged_userns_clone: No such file or directory
fs.inotify.max_queued_events = 1048576
fs.inotify.max_user_watches = 1048576
fs.inotify.max_user_instances = 1048576
kernel.keys.maxkeys = 20000
kernel.keys.maxbytes = 1400000
kernel.pid_max = 4194304

Start at the sysbox-deploy-k8s deployment path and reproduce the failure with the patched or non-mainline kernel described in the report. Inspect the installer and host sysctl configuration around the missing kernel.unprivileged_userns_clone entry, then compare the resulting deployment logs with the successful 5.4.0 case. Done means the worker node completes Sysbox installation without the BackOff restart.