Permission denied when creating new components in WINGS

[dgarijo]

Describe the bug
I am using the docker-compose image to run WINGS. I can create components and initialize them. But the components are created with no execution permissions. As a result, the only way for me to change this is logging in the container and doing chmod on the script files

To Reproduce
Steps to reproduce the behavior:

1. Import a domain (e.g., Caesar's cypher)
2. Create a new component that requires running a scrip
3. Run that component
4. Error: permission denied

Expected behavior
I would like to be able to run the components I create

[varunratnakar]

Hi Daniel,

Thanks for reporting the issue.

I couldn't recreate the chmod bug

• brand new volume
• Imported CaesarCypher from https://wings-workflows.org/domains/students/
• Created a new component, and ran it

I did find a related issue with python components, where it couldn't find python in the container, and needed the run script to have python3 in there

[dgarijo]

Hi Varun,
this issue was not only experienced by me, but by all my students (20+). We had different Operative Systems (I am in Unix, they had Windows and Mac). We all were using the docker image stated in the WINGS repo

I am able to create new components and run them, as long as they don't have any extra scripts (the .sh comes with the right run permissions). If I create and initialize a component with a python script, and I try to run it from bash, then the error appears (permission error in the python script).

I had to docker exec into the container and change the permissions of the python script manually (for every new component created).

[varunratnakar]

Hmm, i was trying on a Mac.. I'll try in the other systems

…

On Fri, 10 Mar 2023, 14:14 Daniel Garijo, ***@***.***> wrote: Hi Varun, this issue was not only experienced by me, but by all my students (20+). We had different Operative Systems (I am in Unix, they had Windows). I am able to create new components and run them, as long as they don't have any extra scripts (the .sh comes with the right run permissions). If I create and initialize a component with a python script, and I try to run it from bash, then the error appears (permission error in the python script). I had to docker exec into the container and change the permissions of the python script manually (for every new component created). — Reply to this email directly, view it on GitHub <#150 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGTB6QTZN47EFGB344P2CZ3W3LSVPANCNFSM6AAAAAAVQMXZSE> . You are receiving this because you commented.Message ID: ***@***.***>

[dgarijo]

In theory the OS should not be the problem.
Maybe we are doing something differently? If you want me to show the steps, I can set up a meeting.