Open lexandera opened 8 months ago
After trying everything I could possibly think of, I went through my backups and checked the latest version I had on my old computer - it was 4.25.2.
So I downgraded my current machine to that version and I haven't experienced a single issue so far.
Whatever the reason behind FUSE failues may be, it appears like it has likely been introduced in 4.26.x
Description
After switching to a new computer I've been experiencing containerized processes getting stuck a few times per day. The most affected process appears to be Vite/NodeJS.
The output of
cat /proc/$PID/stack
always looks like this:[<0>] request_wait_answer+0x15b/0x2b0 [<0>] fuse_simple_request+0x18f/0x2b0 [<0>] fuse_dentry_revalidate+0x138/0x350 [<0>] lookup_fast+0x71/0xe0 [<0>] walk_component+0x1f/0x150 [<0>] link_path_walk.part.0.constprop.0+0x246/0x380 [<0>] path_lookupat+0x3e/0x190 [<0>] filename_lookup+0xed/0x1f0 [<0>] user_path_at_empty+0x3a/0x60 [<0>] do_faccessat+0x11c/0x320 [<0>] do_syscall_64+0x5c/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
I'm using Docker in Hyper-V mode since I need working inotify events inside host mounts (they have not been implemented in WSL2).
Usually the process stays stuck until I restart the VM, but I've seen one case where it got unstuck after a couple of minutes while I was investigating.
Reproduce
So far I can't reproduce the issue on demand. It appears to only happen after a period of inactivity (eg: immediately after a call).
I've tried disabling varoius services that might kick in during times of low activity (power saving, Windows antivirus, cloud backup), but have seen no improvement. There also appears to be nothing immediately obvious in Docker logs, Windows event viewer, or the VM's dmesg output.
Expected behavior
FS operations not causing the process to get stuck.
docker version
docker info
Diagnostics ID
BF8191C3-E265-4D64-AEDE-A7BB6B51A388/20231218212635
Additional Info
The host machine is running Win10 Pro; the VM has had multiple combinations between 4 and 16 cores and 8 to 16GB of RAM assigned to it. I've also purged all the data once through the Troubleshooting pane, as well as diabled all scanning and experimental features.