March 27, 201511 yr Yesterday I updated gfjardim's BTSync container and now it's failing to start with the following message in the log. *** Running /etc/my_init.d/config.sh... *** /etc/my_init.d/config.sh failed with status 127 I tried deleting both the container and image and recreating them, but I get the same error. Anyone else experiencing this or have a solution? Thanks
March 27, 201511 yr Author I found this: Generally it means: 127 - command not found but it can also mean that the command is found, but a library that is required by the command is not found.
March 27, 201511 yr Yesterday I updated gfjardim's BTSync container and now it's failing to start with the following message in the log. *** Running /etc/my_init.d/config.sh... *** /etc/my_init.d/config.sh failed with status 127 I tried deleting both the container and image and recreating them, but I get the same error. Anyone else experiencing this or have a solution? Thanks I will look into this soon.
March 31, 201511 yr Fixed! Thanks for reporting. What was the cause of 127, I'm having a similar issue with a container I'm trying to develop and can't figure it out for the life of me.
April 1, 201511 yr Fixed! Thanks for reporting. What was the cause of 127, I'm having a similar issue with a container I'm trying to develop and can't figure it out for the life of me. In this case, the lack of shebang in the init of the script.
Archived
This topic is now archived and is closed to further replies.