-
Notifications
You must be signed in to change notification settings - Fork 132
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
non-readable python files in a container #1304
Comments
I wasn't able to replicate this:
But I am getting this issue, not sure if it's related: poldracklab/tacc-openneuro#86 |
hm, thank you @jbwexler ! Indeed something odd since it is the same (good one) at docker level:
so somehow those two specific conversions were different on my end for some reason. The only thing which comes to mind is that I could have ran interactively in my session where I have more restrictive umask and that is somehow affected conversion... looking at git log I do not see reflections of that (images were contributed spread in time etc). Overall, I guess this issue could be closed as seems to have no manifestation in the original docker image(s) |
as
|
What happened?
origin:
Since 23.1.1 (ok in 23.1.0) converted to singularity image is not usable due to .py files being not given read permissions to anyone but the root! And as this showed -- there is apparently
python3.1
folder there too!!!NB the python3.1 is I guess a poor man workaround for something
I am yet to find a host with over 30GB of space in
/
to pull the origina docker image to see if permissions are indeed that wrong.What command did you use?
The text was updated successfully, but these errors were encountered: