[FEATURE] Handle known issues with some storage backends (btrfs, zfs, ...) #629
Description
In v5.0.0 we should try to handle some known issues with storage backends more conveniently.
We already have FAQ entries for btrfs and zfs.
At the very least we should check for the storage backend (we already have the runtime-info command) and based on that information emit a warning log.
- automatically add
/dev/mapper:/dev/mappermount on btrfs- check, if, by now, this could work for zfs as well (though k3s may still be lacking zfs support as mentioned also in the FAQ entry)
- if not, emit a warning with a hint to the FAQ entry on ZFS systems
- check, if, by now, this could work for zfs as well (though k3s may still be lacking zfs support as mentioned also in the FAQ entry)
References
- how kind detects whether this is needed or not: https://github.com/kubernetes-sigs/kind/blob/b6bc112522651d98c81823df56b7afa511459a3b/pkg/cluster/internal/providers/docker/util.go#L51-L87