Open josenimo opened 1 year ago
Hi @josenimo,
Sorry for the naive question, but are you able to write files "by hand" (i.e., outside of nextflow) to your drive x
from WSL?
In other words, are you able to do something like:
cd /mnt/x/Jose_Imaging_Data/Exemplar_001/work
mkdir test
cd test
touch hello_world.txt
ln -s hello_world.txt my_symlink.txt
The fact that running the pipeline works on drive c: but not another drive makes me think that the latter was not mounted with correct permissions. Can you do
ls -l /mnt/x/Jose_Imaging_Data/Exemplar_001
whoami
in WSL to see if the file/directory ownership matches the user from whoami
?
Dear @ArtemSokolov,
Thank you for helping me with this not-so-MCMICRO related issue, I appreciate it.
I ran the code you posted, and there seems to be a problem.
First: only josenimo (my WSL/linux username) is seen as the user/group of the C: drive, all other drives it just says root.
Second: Creating a file shows that the file has root permissions, not josenimo persmissions. The user is josenimo, not root.
I read through https://learn.microsoft.com/en-us/windows/wsl/file-permissions, a couple of times and changed the wsl.config to enable metadata, and also did not work
[automount]
options='metadata'
By now I have read a rabbit hole worth of permission documents for linux and wsl, and feel even more confused. Thanks again!
Dear MCMICRO developers,
I am trying to run MCMICRO in my windows machine, through the WSL subsystem, and it is creating some permission problems. I am now just trying to run the Exemplar_001, however it runs into an error executing ashlar.
The folder seems a bit confusing, because I manually downloaded the files, and then tried with downloading the files though nextflow.. but that also did not work.
I was able however to run Exemplar 001 on the C: drive, so I assume the problem is with the external drives, any windows users there could help me? @kbestak
What could cause this symbolic link permission issue??
Thank you in advance :)
Log: nextflow - Copy.log