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

Cannot pass arguments in "run" mode #5

Open
alexhudson opened this issue Sep 3, 2017 · 1 comment
Open

Cannot pass arguments in "run" mode #5

alexhudson opened this issue Sep 3, 2017 · 1 comment
Labels

Comments

@alexhudson
Copy link
Owner

The wrapper automatically passes arguments through to the runtime container, but in run mode it just drops them on the floor. Both should work the same way.

@alexhudson alexhudson added the bug label Sep 3, 2017
alexhudson added a commit that referenced this issue Sep 3, 2017
Because of limitations in the cli parser, we need to provide further arguments
after stowage arguments, using --
@alexhudson
Copy link
Owner Author

I now have a way of doing this, unfortunately it's a bit of a work-around. I want to be able to write:

stowage run basic-bash --version

... for example, but any options I pass get parsed by urfave/cli (see urfave/cli#663). However, this can be hacked around like this:

stowage run basic-bash -- --version

urfave/cli stops parsing at --, and if that is the first argument stowage finds, it simply drops it from the list, giving us the original list of arguments we wanted.

Leaving this open until we find a better way of doing it.

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

No branches or pull requests

1 participant