I am experiencing an issue with Docker on my macOS machine equipped with an M3 processor. When running scripts, such as composer, within a container, I randomly encounter error 137. Sometimes the script fails immediately upon execution, sometimes it passes, and at other times it fails during operation.
In my Docker Desktop settings, I have selected VirtioFS. Generally, Docker seems to be sluggish, and I suspect that the issue is related to bind volumes, which, as I understand, is associated with file management.
The problem occurs across different projects, so it's unlikely to be due to faulty configuration. Here is an example of my configuration:
Description
I am experiencing an issue with Docker on my macOS machine equipped with an M3 processor. When running scripts, such as composer, within a container, I randomly encounter error 137. Sometimes the script fails immediately upon execution, sometimes it passes, and at other times it fails during operation.
In my Docker Desktop settings, I have selected VirtioFS. Generally, Docker seems to be sluggish, and I suspect that the issue is related to bind volumes, which, as I understand, is associated with file management.
The problem occurs across different projects, so it's unlikely to be due to faulty configuration. Here is an example of my configuration:
I did docker full reinstall and the situation is like before that. Any help or suggestions to resolve this issue would be greatly appreciated.
Reproduce
docker compose build docker compose up -d
docker compose exec -it app ./vendor/bin/phpunit tests/Unit
Expected behavior
No response
docker version
docker info
Diagnostics ID
2C1E65EC-6476-4336-8080-1B1377D132F5/20240603165644
Additional Info
No response