fly hijack should search harder for a shell #5521
tremblaysimon
started this conversation in
General
Replies: 1 comment 1 reply
-
|
This would be nice to have. 👍 I'm not going to re-open the issue because it's unlikely that we would prioritize this ourselves (our roadmap is pretty packed), but a PR for this would definitely be accepted, and I'm happy to help along the way. Here's my comment from last time this came up that provides some guidance/context for anyone interested: #4755 (comment) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
By default
fly hijackcommand without command arg will try to startbashin the hijacked container. If the container doesn't containbashit will produce an error. So we will try to hijack with /bin/sh instead.It's not a command that we use everyday and in Windows world (with git bash terminal for example) the command
fly -t your-target hijack -u build-url /bin/shwill not work (we can use insteadfly -t your-target hijack -u build-url shand it will work...)It should try to open
shifbashisn't found, at least. Maybe it should be configurable like it is mentioned in the old unresolved and closed issue #1073?It's not a blocking issue, but it would be a nice feature to have. It would be convenient.
What do you think about that? Should we reopen #1073?
Beta Was this translation helpful? Give feedback.
All reactions