Closed sudotejas closed 3 years ago
@drnic The script is already checked out with the executable permissions set. So unless someone's umask overrides the settings the file is already executable. Also since the code has been changed to execute the shell instead of the file directly, the execute permission should not be needed anymore. Is there something I am missing here?
It’s from 2019. Let’s close and reopen if it appears again.
It might have been a local issue for @sudotejas
Hopefully ok to close. If anyone else spots this issue and needs to chmod these files please let us know.
The error that comes up when the file does not have executable permissions. Backend error: Exit status: 500, message: {"Type":"","Message":"runc exec: exit status 1: exec failed: container_linux.go:345: starting container process caused \"exec: \\"./task-scripts/task_show_uname.sh\\": permission denied\"\n","Handle":"","ProcessID":"","Binary":""} errored