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
Obviously the last line should cause a Permission denied error, and that is what happens locally. But running via this action using this minimal workflow, I get no error - Python can read the unreadable file.
I wonder whether this is because the tox tests are running as some privileged user, for whom setting the user read permission is not effective?
The text was updated successfully, but these errors were encountered:
matthew-brett
changed the title
Unable to set file as read-only inside tox container
Unable to set file as unreadable inside tox container
Aug 30, 2023
We can either do this for everybody in the Dockerfile using RUN adduser … and then USER … or in the shell script as an optional feature configured by an env variable so only if you specify a username, we'll create it and use it to run tests.
I'm a little bit afraid that doing that in Dockefile might break other workflows.
I have a Python module that relies on setting permissons to a file as unreadable.
Unfortunately, it looks like this is not possible inside the tox container.
Here's the minimal reproducer : https://github.com/matthew-brett/test-actions/blob/main/tox.ini
In particular, I have this test in my
tox.ini
file:Obviously the last line should cause a
Permission denied
error, and that is what happens locally. But running via this action using this minimal workflow, I get no error - Python can read the unreadable file.I wonder whether this is because the tox tests are running as some privileged user, for whom setting the user read permission is not effective?
The text was updated successfully, but these errors were encountered: