Mounting "modern" FUSE filesystems (with filenames > 255 chars) into gVisor containers

[abhagwat]

Description

We at Modal Labs run gVisor containers for our users. Our users can mount various storage options into their containers, including cloud object buckets (https://modal.com/docs/guide/cloud-bucket-mounts).

Under the hood, we use AWS's mountpoint-s3 tool (https://github.com/awslabs/mountpoint-s3) which mounts remote a cloud bucket as a FUSE filesystem on the host.

The problem: this FUSE filesystem allows filenames longer than 255 chars. Such long object names are also legal in cloud object storage. gVisor however doesn't allow such long names. So, when we mount such a cloud bucket (with long object names) inside the container, gVisor panics.

We'd like some advice here: is there any path to handling such situations better within gVisor?

Is this feature related to a specific bug?

No response

Do you have a specific solution in mind?

No.

[ayushr2]

@nixprime fixed this issue in 65762f8; it removes the name length constraint from ParseDirents() as you pointed out. Could you verify that the panic you were seeing is gone?