Sandbox ID or Build ID
No response
Environment
E2B SDK version: 2.21.0
OS: Ubuntu 24.04
Sandbox ID: idq0efx5b3ygzpy5kw5e7
Local host directory: /home/supabase-project
Sandbox mount path: /mnt/shared-data
Timestamp of the issue
Tue Jun 16 05:20:31 PM CST 2026
Frequency
Happens every time
Expected behavior
When initializing the asynchronous persistent volume connection, the sandbox starts successfully and the bidirectional real-time sync listener is active for both local /home/supabase-project and sandbox /mnt/shared-data.
Expected behavior
All files, nested subfolders and full directory structure from the host’s target folder should be fully synced and visible inside the sandbox mount path after initialization completes.
Actual behavior
However , only a small subset of files & subdirectories from the host’s full directory tree are mirrored into the sandbox. Most folders and files under /home/supabase-project are missing inside /mnt/shared-data with no warning, error logs or sync timeout prompts.
Issue reproduction
1.Initialize E2B sandbox with persistent volume bidirectional sync enabled
2.Point local watch path to /home/supabase-project (contains dozens of nested folders, source code, config files)
3.Sandbox mount target set to /mnt/shared-data
4.Wait for sync ready log output
5.List files inside sandbox /mnt/shared-data — only partial directories appear, most content missing
Additional context
Log Snippet
Initializing connection to E2B asynchronous persistent volume...
E2B sandbox started successfully! ID: idq0efx5b3ygzpy5kw5e7
👀 Bidirectional real-time sync ready, listening local: /home/supabase-project
👀 Deep listening for internal changes on Sandbox path: /mnt/shared-data
❌ 'utf-8' codec can't decode byte 0xd1 in position 1: invalid continuation byte
No filtering or exclude rules configured. There is no obvious pattern for which subdirectories get synced; random partial content is mirrored instead of the full directory.
Sandbox ID or Build ID
No response
Environment
E2B SDK version: 2.21.0
OS: Ubuntu 24.04
Sandbox ID: idq0efx5b3ygzpy5kw5e7
Local host directory: /home/supabase-project
Sandbox mount path: /mnt/shared-data
Timestamp of the issue
Tue Jun 16 05:20:31 PM CST 2026
Frequency
Happens every time
Expected behavior
When initializing the asynchronous persistent volume connection, the sandbox starts successfully and the bidirectional real-time sync listener is active for both local /home/supabase-project and sandbox /mnt/shared-data.
Expected behavior
All files, nested subfolders and full directory structure from the host’s target folder should be fully synced and visible inside the sandbox mount path after initialization completes.
Actual behavior
However , only a small subset of files & subdirectories from the host’s full directory tree are mirrored into the sandbox. Most folders and files under /home/supabase-project are missing inside /mnt/shared-data with no warning, error logs or sync timeout prompts.
Issue reproduction
1.Initialize E2B sandbox with persistent volume bidirectional sync enabled
2.Point local watch path to /home/supabase-project (contains dozens of nested folders, source code, config files)
3.Sandbox mount target set to /mnt/shared-data
4.Wait for sync ready log output
5.List files inside sandbox /mnt/shared-data — only partial directories appear, most content missing
Additional context
Log Snippet
Initializing connection to E2B asynchronous persistent volume...
E2B sandbox started successfully! ID: idq0efx5b3ygzpy5kw5e7
👀 Bidirectional real-time sync ready, listening local: /home/supabase-project
👀 Deep listening for internal changes on Sandbox path: /mnt/shared-data
❌ 'utf-8' codec can't decode byte 0xd1 in position 1: invalid continuation byte
No filtering or exclude rules configured. There is no obvious pattern for which subdirectories get synced; random partial content is mirrored instead of the full directory.