Skip to content
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

crictl exec: cannot parse command args #305

Closed
vrothberg opened this issue May 7, 2018 · 5 comments · Fixed by #306
Closed

crictl exec: cannot parse command args #305

vrothberg opened this issue May 7, 2018 · 5 comments · Fixed by #306

Comments

@vrothberg
Copy link
Contributor

crictl exec isn't able to parse arguments of a specified command starting the "-" as they're interpreted as flags of crictl exec instead of just passing them to the command.

Version: Tried with latest crictl (i.e., commit 7f1936f).

Reproduce with crictl exec ID ls -la

FATA[0000] flag provided but not defined: -la 
@vrothberg
Copy link
Contributor Author

The problem is actually a bit worse: when doing something like crictl exec ID ls -i, the command will be executed interactively due to the -i argument. I think we need to move away from urfave/cli, which doesn't seem to support such use-cases.

@vrothberg
Copy link
Contributor Author

I think we need to move away from urfave/cli, which doesn't seem to support such use-cases.

I have to correct my statement. Vendoring in a more recent version of urfave/cli did the trick, see #306.

@vrothberg
Copy link
Contributor Author

@feiskyer Can we add the two patches into the release-1.10 branch? Soon, we'll update to K8s 1.10, where we need those change for crictl. Is there a specific workflow in the cri-tools project for backports?

@feiskyer
Copy link
Member

feiskyer commented May 8, 2018

@vrothberg Could you create a cherry pick PR for release-1.10?

@vrothberg
Copy link
Contributor Author

@vrothberg Could you create a cherry pick PR for release-1.10?

Sure. I'll prepare one and ping you there. Thanks for the quick reply!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants