"no command specified" on every command about dockerize HOT 13 CLOSED

@doodyparizada

from dockerize.

i understand now that i was missing the app to be executed after the template finished processing.
the help line is a little misleading:

$ dockerize -h
Usage of dockerize:
  -delims string
        template tag delimiters. default "{{":"}}"
  -stderr value
        Tails a file to stderr. Can be passed multiple times
  -stdout value
        Tails a file to stdout. Can be passed multiple times
  -template value
        Template (/template:/dest). Can be passed multiple times
  -version
        show version

• i'm missing an "how to execute" line at the top of the help file
• also, i'd like to have a way to just generate a template without executing anything

from dockerize.

Right now I'm bypassing this by passing true to the app part of the command, practically making dockerize execute a no-op:

$ 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 SIGTERMing.

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?

from dockerize.

@oryband I think some kind of a -dry-run feature would be useful. Good idea.

from dockerize.

The no command specified could be improved as well.

from dockerize.

I know it's not backward compatible, but I would prefer that dockerize's default behaviour would be to not expect a command be given (i.e. default -dry-run) so it just renders the template. If you want to give a command, you would have to specify --command="XXX XXX"

from dockerize.

@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 :/dest portion.

from dockerize.

@jwilder thanks!

however, I think adding an example of the hack I did above is a good idea (providing true as a command). Some people (like myself) would only like to use the templating feature of dockerize, without the execution part. If we're keeping the command as required, we should at least provide an example how to bypass it.

from dockerize.

@oryband It sounds like you may be better off using jwilder/docker-gen instead of dockerize.

from dockerize.

@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.

from dockerize.

@md5 You're right. That was a silly suggestion on my part.

from dockerize.

@md5 why are you talking to yourself? :)

from dockerize.

Why not achieve maximum silliness?

from dockerize.