"WARNING: cannot create user data directory: cannot determine SELinux status: failed to obtain SELinux mount path" warning by snap

I'm running Ubuntu 20.04 on WSL2, and whenever I run helm I get the following warning:

cmd_run.go:1046: WARNING: cannot create user data directory: cannot determine SELinux status: failed to obtain SELinux mount path: incorrect number of tail fields, expected 3 but found 4

Searching for this error has not produced anything meaningful. How can I get rid of this warning?

Ubuntu version:

$ lsb_release -aNo LSB modules are available.Distributor ID: UbuntuDescription:    Ubuntu 20.04.6 LTSRelease:        20.04Codename:       focal

Helm version (warnings removed):

$ helm versionversion.BuildInfo{Version:"v3.10.1", GitCommit:"9f88ccb6aee40b9a0535fcc7efea6055e1ef72c9", GitTreeState:"clean", GoVersion:"go1.18.7"}

I've also reported this as an issue to helm, and a collaborator thinks it has to do with snap, and not necessarily helm.

So I ran helm with SNAP_CONFINE_DEBUG=yes, and this is the output I got:

$ SNAP_CONFINE_DEBUG=yes helm ls2023/04/14 02:34:53.395489 system_key.go:129: cannot determine nfs usage in generateSystemKey: cannot parse mountinfo: incorrect number of tail fields, expected 3 but found 42023/04/14 02:34:53.399251 cmd_run.go:1046: WARNING: cannot create user data directory: cannot determine SELinux status: failed to obtain SELinux mount path: incorrect number of tail fields, expected 3 but found 4DEBUG: -- snap startup {"stage":"snap-confine enter", "time":"1681419893.460473"}DEBUG: umask reset, old umask was  022DEBUG: security tag: snap.helm.helmDEBUG: executable:   /snap/snapd/18596/usr/lib/snapd/snap-execDEBUG: confinement:  classicDEBUG: base snap:    core18DEBUG: ruid: 1000, euid: 0, suid: 0DEBUG: rgid: 1000, egid: 1000, sgid: 1000DEBUG: apparmor extensions to the system are not availableDEBUG: -- snap startup {"stage":"snap-confine mount namespace start", "time":"1681419893.461157"}DEBUG: preparing classic execution environmentDEBUG: -- snap startup {"stage":"snap-confine mount namespace finish", "time":"1681419893.461195"}DEBUG: set_effective_identity uid:1000 (change: yes), gid:1000 (change: yes)DEBUG: creating user data directory: /home/samslk/snap/helm/372DEBUG: ruid: 1000, euid: 1000, suid: 0DEBUG: setting capabilities bounding setDEBUG: regaining SYS_ADMINDEBUG: loading bpf program for security tag snap.helm.helmDEBUG: read 14 bytes from /var/lib/snapd/seccomp/bpf//snap.helm.helm.binDEBUG: clearing SYS_ADMINDEBUG: execv(/snap/snapd/18596/usr/lib/snapd/snap-exec, /snap/snapd/18596/usr/lib/snapd/snap-exec...)DEBUG:  argv[1] = helmDEBUG:  argv[2] = lsDEBUG: umask restored to  022DEBUG: working directory restored to /home/samslk/experiments/misc/helm-tutorialDEBUG: -- snap startup {"stage":"snap-confine to snap-exec", "time":"1681419893.461324"}...normal helm output from this point onwards

So it indeed looks like the warnings are coming from snap, as the helm executable is not started by snap until later.

How can I fix/suppress this?