Request: FUSE or NFSv3 kernel support in VM instances

[angel-manuel]

Summary

Morph Cloud VM instances currently lack both FUSE and NFSv3 kernel support, making it impossible to mount user-space filesystems like AgentFS inside VMs.

Current State

Checked /proc/filesystems on a Morph VM — relevant entries:

nodev   nfs
nodev   nfs4

Missing:

• fuse / fuseblk — not in /proc/filesystems, /dev/fuse doesn't exist
• NFSv3 client — mount -t nfs -o vers=3 ... returns "Protocol not supported" (likely CONFIG_NFS_V3 not set in kernel config)

What works:

• nfs4 is listed but only useful if the server speaks NFSv4
• Creating /dev/fuse via mknod succeeds but FUSE mounts fail since the kernel module isn't compiled in

Use Case

We run AgentFS (SQLite-backed virtual filesystem by Turso) inside Morph VMs to provide persistent workspaces for AI agents. AgentFS supports two mount backends:

1. FUSE (default on Linux) — needs kernel FUSE support
2. NFS (NFSv3 server over localhost) — needs NFSv3 client in the kernel

Neither works on current Morph VMs.

Request

Please add one or both of:

1. FUSE support — compile CONFIG_FUSE_FS=y into the kernel and ensure /dev/fuse is created at boot. This is the most versatile option as it enables any FUSE filesystem (sshfs, s3fs, agentfs, etc.)

2. NFSv3 client support — compile CONFIG_NFS_V3=y into the kernel. This enables mounting NFSv3 servers running on localhost.

FUSE would be preferred as it's more broadly useful.

Environment

• Snapshot base: Debian-based Morph VM image
• Kernel: stock Morph kernel (no /proc/version available, no /boot/config-*)
• Tested on instance morphvm_i42smlng