You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed in the last week or two that files in volume mounts in my containers don't seem to sync changes as quickly as usual, sometimes I'll leave and come back minutes after saving a file on the host OS and it still hasn't shown up inside the container. I often have to restart the container entirely to update the contents of a volume mount defined in the docker-compose.yml. This is happening both in containers based on both debian and ubuntu images.
Looks like the automatic diagnostic report also failed.
To Reproduce
Run a container, any container
setup a volume mount in docker-compose
change a file on host os
Wait to see change appear inside docker container os
Expected behavior
File mounts synchronize very quickly, within seconds.
Seeing the same thing myself while trying to use a promtail container to siphon logs from a developer application running on the host. (We use containers to support a development environment, while keeping the actual code under test running natively.) Opening a terminal to the container and tail -f reproduces the same symptoms, so it's not container specific.
Describe the bug
I've noticed in the last week or two that files in volume mounts in my containers don't seem to sync changes as quickly as usual, sometimes I'll leave and come back minutes after saving a file on the host OS and it still hasn't shown up inside the container. I often have to restart the container entirely to update the contents of a volume mount defined in the docker-compose.yml. This is happening both in containers based on both debian and ubuntu images.
Looks like the automatic diagnostic report also failed.
To Reproduce
Expected behavior
File mounts synchronize very quickly, within seconds.
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.5.1
Commit: 4cfac15e1080617c70eb163966e1cb2009dac1c2 (v1.5.1)
System info:
macOS: 14.1.1 (23B81)
CPU: amd64, 12 cores
CPU model: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Model: MacBookPro16,1
Memory: 32 GiB
Diagnostic report failed: get presigned url: [api] size is invalid
(500 Internal Server Error)
Screenshots and additional context (optional)
No response
The text was updated successfully, but these errors were encountered: