setsid: can't execute './test.sh': Exec format error
I tried to execute setsid ./test.sh
command on Alpine OS in a docker container.
And it says 'Exec format error'. then I added a header bang '
#!/usr/bin/env bash' to that script. It works.
But the same command and script without header on centos6 works well.
I've digged into it deeply. Seems that setsid is a system call which use execvp to execute command, execvp will treat the script as an execute file.
My script.sh has execute permission and can run with './script.sh'. Why does the script behave differently on alpine and centos?
bash
add a comment |
I tried to execute setsid ./test.sh
command on Alpine OS in a docker container.
And it says 'Exec format error'. then I added a header bang '
#!/usr/bin/env bash' to that script. It works.
But the same command and script without header on centos6 works well.
I've digged into it deeply. Seems that setsid is a system call which use execvp to execute command, execvp will treat the script as an execute file.
My script.sh has execute permission and can run with './script.sh'. Why does the script behave differently on alpine and centos?
bash
1
I would assume that alpine doesn't know that your script is a executable (it is just a text file after all). bash is the executable that runs the script - so your bang solves it, or you could run it like this: setsid bash test.sh. CentOs might be a bit more clever and knows what you want to do
– Milos Matovic
Nov 12 at 12:51
1
Note that while it may work on Centos, you don't really know ifbash
is really the shell being run (in this case, it was most likely run by/bin/sh
instead). Adding a shebang is considered best practice as this explicitely states which program should run your script
– Aserre
Nov 12 at 13:08
add a comment |
I tried to execute setsid ./test.sh
command on Alpine OS in a docker container.
And it says 'Exec format error'. then I added a header bang '
#!/usr/bin/env bash' to that script. It works.
But the same command and script without header on centos6 works well.
I've digged into it deeply. Seems that setsid is a system call which use execvp to execute command, execvp will treat the script as an execute file.
My script.sh has execute permission and can run with './script.sh'. Why does the script behave differently on alpine and centos?
bash
I tried to execute setsid ./test.sh
command on Alpine OS in a docker container.
And it says 'Exec format error'. then I added a header bang '
#!/usr/bin/env bash' to that script. It works.
But the same command and script without header on centos6 works well.
I've digged into it deeply. Seems that setsid is a system call which use execvp to execute command, execvp will treat the script as an execute file.
My script.sh has execute permission and can run with './script.sh'. Why does the script behave differently on alpine and centos?
bash
bash
asked Nov 12 at 12:33
Reminia Scarlet
11
11
1
I would assume that alpine doesn't know that your script is a executable (it is just a text file after all). bash is the executable that runs the script - so your bang solves it, or you could run it like this: setsid bash test.sh. CentOs might be a bit more clever and knows what you want to do
– Milos Matovic
Nov 12 at 12:51
1
Note that while it may work on Centos, you don't really know ifbash
is really the shell being run (in this case, it was most likely run by/bin/sh
instead). Adding a shebang is considered best practice as this explicitely states which program should run your script
– Aserre
Nov 12 at 13:08
add a comment |
1
I would assume that alpine doesn't know that your script is a executable (it is just a text file after all). bash is the executable that runs the script - so your bang solves it, or you could run it like this: setsid bash test.sh. CentOs might be a bit more clever and knows what you want to do
– Milos Matovic
Nov 12 at 12:51
1
Note that while it may work on Centos, you don't really know ifbash
is really the shell being run (in this case, it was most likely run by/bin/sh
instead). Adding a shebang is considered best practice as this explicitely states which program should run your script
– Aserre
Nov 12 at 13:08
1
1
I would assume that alpine doesn't know that your script is a executable (it is just a text file after all). bash is the executable that runs the script - so your bang solves it, or you could run it like this: setsid bash test.sh. CentOs might be a bit more clever and knows what you want to do
– Milos Matovic
Nov 12 at 12:51
I would assume that alpine doesn't know that your script is a executable (it is just a text file after all). bash is the executable that runs the script - so your bang solves it, or you could run it like this: setsid bash test.sh. CentOs might be a bit more clever and knows what you want to do
– Milos Matovic
Nov 12 at 12:51
1
1
Note that while it may work on Centos, you don't really know if
bash
is really the shell being run (in this case, it was most likely run by /bin/sh
instead). Adding a shebang is considered best practice as this explicitely states which program should run your script– Aserre
Nov 12 at 13:08
Note that while it may work on Centos, you don't really know if
bash
is really the shell being run (in this case, it was most likely run by /bin/sh
instead). Adding a shebang is considered best practice as this explicitely states which program should run your script– Aserre
Nov 12 at 13:08
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53262304%2fsetsid-cant-execute-test-sh-exec-format-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53262304%2fsetsid-cant-execute-test-sh-exec-format-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I would assume that alpine doesn't know that your script is a executable (it is just a text file after all). bash is the executable that runs the script - so your bang solves it, or you could run it like this: setsid bash test.sh. CentOs might be a bit more clever and knows what you want to do
– Milos Matovic
Nov 12 at 12:51
1
Note that while it may work on Centos, you don't really know if
bash
is really the shell being run (in this case, it was most likely run by/bin/sh
instead). Adding a shebang is considered best practice as this explicitely states which program should run your script– Aserre
Nov 12 at 13:08