Trinity output directory can be erased only with root privileges

Question

[langziv]

Hello

I didn't see information in the documentation about that issue. Can the program be used or installed so that no root privileges will be required in order to erase the output directory?

[GenoMax]

Have you checked to see if you need to simply change the permissions to allow the deletion? Output directories normally will be created as owned by the account that is running the program (which should be your account, unless your system is set up differently). If not on your server then you will need to ask your local admins.

[langziv]

The output directory's permissions? I tried and it didn't work. It never happened before with another program, so I assumed it has to do with Trinity.

[GenoMax]

Can you show us the permissions and the exact command? What are you not able to do? Delete the directory or files within?

Answer 1

[Philipp Bayer]

My guess is that Trinity was run via Docker/Singularity and the Docker container uses user ID 1000 for running jobs. New files outside the container will be written by the user with that ID which usually is root.

To fix:

docker run -u $(id -u):$(id -g) (rest of your command)