Because the executable is proprietary (and a bit legacy I would say) and full of telemetry, undocumented and the cloud service has no CLI, WebDAV or rclone support. I do not want to run something like that on my personal computer and I do not know how to use bwrap properly and don’t want to risk it. I have since switched over to a podman container but I encounter the same problem, the folder is empty on the host (See my post here: https://lemmy.ml/post/22215540).

I have already tried that. It doesn’t work, the cloud folder is empty on the host.

Yes.

I am using the binary. Just running it inside a container instead of a VM.

overlay fs?

Yes.

Since originally writing the post I have switched to a rootless podman container. Running it how I did before (inside a VM) would simply yield user_id=1000,group_id=1000 I think.

rw,nosuid,nodev,relatime,user_id=0,group_id=0

Thank you!

Fair. I will try NFS if anything else fails. Thanks :)

I strongly disagree why this would not be beneficial. Could you expand?

I don’t understand what you mean with the content disappearing when you mount the virtiofs on the guest - isn’t the mount empty when bound, untill the guest populates it?

Sorry I made a mistake in the original post. I wanted to say on the host instead of on the guest. My bad.

Yes, you are correct, the folder is empty until I log in insde the cloud application on the guest.

does it require local storage or support remote?

What do you mean? The cloud drive is a network drive basically. It only downloads files on demand.

if guest os is linux, nfs will probably do

This is what others have suggested and what I will probably do if the method below fails.

podman/docker seems to be the proper tool for you here

Yesterday I actually tried to spin a podman container hoping it would work but I encountered the following problem when trying to propagate mounts: https://lemmy.ml/post/22215540

Could you please assist me there if you have further ideas? Thank you :)

Keep in mind that a screwup could be interpreted by the sync client as mass-deletes

I am VERY aware of this *sweating*