Skip to content

installtion on read only file system#94

Open
EricDeveaud wants to merge 4 commits into
RosettaCommons:mainfrom
EricDeveaud:RWFS
Open

installtion on read only file system#94
EricDeveaud wants to merge 4 commits into
RosettaCommons:mainfrom
EricDeveaud:RWFS

Conversation

@EricDeveaud

Copy link
Copy Markdown

Hello,

we installed RFantiboy on our cluster on read only shared disk. and have problems with user trying to write files on this FS

our users hit some rights problem when the tools tries to writtes some hydra//omega outputs logs.

 PermissionError: [Errno 13] Permission denied: 'outputs/2026-04-17’ 

fixing this problem #a22641133c3584e02ff8e87b0cbc4d55f0f74df1 by settings hydra config to spit outputs to HOME/.rfantibody

but then we noticed an other problems, with .pkl file caching.

#2dba312c9c27e2094f48978f741c4d06a706ddab allow to also cache generated .pkl files to same destination than outputs.

regards

Eric

@roccomoretti

roccomoretti commented Apr 20, 2026

Copy link
Copy Markdown
Member

Thanks for tackling this -- I just had issues with this myself.

Can't speak for others, but for me personally, I would prefer to have the outputs/ logs somewhere in the running directory (e.g. near the same location as the structure files), rather than accumulating a progressive number of additional files a hidden directory somewhere. -- Though I don't know how easy that would be to implement.

Having the one-and-done cache of the generated files (versus files that accumulate over multiple runs) in the home directory is fine, though ideally that would be a fall-back. (If you install centrally in a multi-user system, ideally someone with write access could generate the cache once in the central location and have it apply for all users.)

@EricDeveaud

Copy link
Copy Markdown
Author

working dir was my initial idea, but I wasn't abble to determine how to implement it ;-(

cached file are really small. I can generate those one, but I'm not sure to be bio compliant enough to generate all the required ones ;-)
I prefer to have competent people abble to handle it.

regards

Eric

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants