Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Volume mounts don't seem to be synchronizing file changes quickly #1171

Closed
rgasper opened this issue May 10, 2024 · 3 comments
Closed

Volume mounts don't seem to be synchronizing file changes quickly #1171

rgasper opened this issue May 10, 2024 · 3 comments
Labels
t/bug Something isn't working

Comments

@rgasper
Copy link

rgasper commented May 10, 2024

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

  1. Run a container, any container
  2. setup a volume mount in docker-compose
  3. change a file on host os
  4. Wait to see change appear inside docker container os

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

@rgasper rgasper added the t/bug Something isn't working label May 10, 2024
@lieut-data
Copy link

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.

@kdrag0n
Copy link
Member

kdrag0n commented May 12, 2024

Please share a sample project / commands to reproduce this.

@kdrag0n
Copy link
Member

kdrag0n commented May 12, 2024

Duplicate of #1148 so please reply there.

@kdrag0n kdrag0n closed this as completed May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants