-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"iocell exec" only works for commands without arguments #28
Comments
Thanks for the report! Would you have a patch or PR coming too? |
@kraileth Try it without the quotes, e.g. (Sorry for being late to the party, but I'm only now getting into this jail thingy. :) |
rostwald
added a commit
to rostwald/iocell
that referenced
this issue
Feb 19, 2024
The command handed over to jexec is already quoted; this might cause confusion (see bartekrutkowski#28). This addition clarifies what goes on behind the scenes and also gives a hint to escape any quotes that might be needed in the command.
rostwald
added a commit
to rostwald/iocell
that referenced
this issue
Sep 4, 2024
The command handed over to jexec is already quoted; this might cause confusion (see bartekrutkowski#28). This addition clarifies what goes on behind the scenes and also gives a hint to escape any quotes that might be needed in the command.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issuing "iocell exec [running jail] [command]" works as long as [command] does not contain any spaces (e.g. "ls" works but "ls -l" doesn't". Iocage had this problem as well but obviously was able to fix it in the beginning of the year (see here: iocage/iocage#17).
The problem is most likely that iocell uses jexec without having it run a shell. On a German bsd forum I found a hint on how to use jexec properly (i.e. supplying "sh -c" and then the command and arguments). This seems to work.
Here are the details (except for version info I left out the output from commands that behave normally):
The text was updated successfully, but these errors were encountered: