Commands: Build

You can build repositories by using docker-template build, which accepts multiple types of repository formats (the same way that traditional Docker does.) Inferring data from either your opts.yml files or file system to detrmine how to proceed.

Example Formats

• user/image
• user/image:tag
• image:tag
• image

Usage

Usage:
  docker-template build [REPOS [OPTS]]

Options:
  [--diff], [--no-diff]        # Build only modified repositories.
  [--profile], [--no-profile]  # Profile Memory.
  [--tty], [--no-tty]          # Enable TTY Output.
  [--push], [--no-push]        # Push Repo After Building.
  [--cache], [--no-cache]      # Cache your repositories to cache.
  [--mocking], [--no-mocking]  # Disable Certain Actions.
  [--clean], [--no-clean]      # Cleanup your caches.
  [--help], [--no-help]        # Output this.

Build all (or some) of your repositories.

You can send as many repos/images as you like, or you can send none, the lack of any repos/images will result in all of the possible images being built from your repos/ folder. This is good for automated building. NOTE: When building images we sort them, in that scratch images are built first, normal images are built second and aliases are done last, so that if you have dependencies within your dependencies hopefully they will get built first, however this is not always likely if your images rely on another normal image. In that case you might want to send a manual list.

By Diff

Sending the --diff flag to build will force Docker Template to use Git to pull the last commit and get a diff of the files that have changed, so that it will filter the repos you send (or if you send none -- all of the repos) and build only what has changed.