-
Notifications
You must be signed in to change notification settings - Fork 413
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
"no command specified" on every command #13
Comments
i understand now that i was missing the app to be executed after the template finished processing.
|
Right now I'm bypassing this by passing $ docker -template x:y true && my_app
# instead of doing this, which is undesirable in my case:
$ docker -template x:y my_app However, this is a hack. This is sometimes necessary because letting dockerize execute the app can sometimes create problems and errors. For example when It feels like dockerize is trying to achieve two things at once, instead of going the unix way: Splitting the features into two separate tools, which can be bundled together if necessary. wdyt? |
@oryband I think some kind of a |
The |
I know it's not backward compatible, but I would prefer that |
@oryband I've updated the usage as well as made command optional as well. @doodyparizada Command is not optional. You can render templates to standard output for debugging by leaving off the |
@jwilder thanks! however, I think adding an example of the hack I did above is a good idea (providing |
@oryband It sounds like you may be better off using |
@md5 I did at first, but it requires mounting the docker socket file in order to fetch environment variables. This is kinda overkill for the purpose of templating. There is no other golang cli template tool available beside these two tools. |
@md5 You're right. That was a silly suggestion on my part. |
@md5 why are you talking to yourself? :) |
Why not achieve maximum silliness? |
doc: update README
running this inside an ubuntu latest image:
any idea what is wrong? the output is really unhelpful
The text was updated successfully, but these errors were encountered: