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
first of all, many thanks for all the work put into this awesome project!
I have the following setup:
Colima is running with a directory mounted into the VM as writable using colima start --mount <dir>:w.
I have a docker container running with a subdirectory <subdir> of <dir> mounted via a bind mount.
Inside the container, I run a node process which is supposed to write a modest amount (~ 400) of generated text files into yet another subdirectory of <subdir>.
Unfortunately, the process fails with EPERM: operation not permitted, open <file>. The <file> is different each time, but the number of files written before the error is always 233 or 234. I made sure that everyone (the actual computer, the VM and the container) sees the folder as writable to rule out that it is an actual problem of permissions. With Docker Desktop, no such error occurs. ulimit -n returns 256 on the computer, 1024 on the VM and 1048576 in the container.
Once again, many thanks for your efforts!
Best,
Jakub
The text was updated successfully, but these errors were encountered:
Hi everyone,
first of all, many thanks for all the work put into this awesome project!
I have the following setup:
colima start --mount <dir>:w
.<subdir>
of<dir>
mounted via a bind mount.<subdir>
.Unfortunately, the process fails with
EPERM: operation not permitted, open <file>
. The<file>
is different each time, but the number of files written before the error is always 233 or 234. I made sure that everyone (the actual computer, the VM and the container) sees the folder as writable to rule out that it is an actual problem of permissions. With Docker Desktop, no such error occurs.ulimit -n
returns 256 on the computer, 1024 on the VM and 1048576 in the container.Once again, many thanks for your efforts!
Best,
Jakub
The text was updated successfully, but these errors were encountered: