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
Hey there! Thanks for the image, for some reason tox don't want to discover some Python versions on my machine. The image saved my day.
However, I believe there's a problem when running this image on Linux hosts.
On Mac, the example command simply works out of the box, because Docker on Mac does some GID/UID reassigning magic (I didn't research too much about it) when mounting files from the host filesystem into a container.
On Linux hosts, this doesn't happen. An attempt to run this image will result in PermissionError: [Errno 13] Permission denied: '/tests/.tox/.pkg/file.lock' or something like that, because the /tests directory and all its content will belong to the host user, and container user won't have any permissions in this directory.
At least this is how the situation looks on my end. I solved it by changing the container user with -u 1000 flag. Maybe this should be mentioned in the docs. Maybe there's a better approach. Anyway, I wanted to share this with anyone who might get into this trouble.
The text was updated successfully, but these errors were encountered:
Hey there! Thanks for the image, for some reason tox don't want to discover some Python versions on my machine. The image saved my day.
However, I believe there's a problem when running this image on Linux hosts.
On Mac, the example command simply works out of the box, because Docker on Mac does some GID/UID reassigning magic (I didn't research too much about it) when mounting files from the host filesystem into a container.
On Linux hosts, this doesn't happen. An attempt to run this image will result in
PermissionError: [Errno 13] Permission denied: '/tests/.tox/.pkg/file.lock'
or something like that, because the/tests
directory and all its content will belong to the host user, and container user won't have any permissions in this directory.At least this is how the situation looks on my end. I solved it by changing the container user with
-u 1000
flag. Maybe this should be mentioned in the docs. Maybe there's a better approach. Anyway, I wanted to share this with anyone who might get into this trouble.The text was updated successfully, but these errors were encountered: