anchor.diff:  Strangely enough the email field is *mandatory* for the current version of the spotify Docker-maven-plugin to work correctly, so watch out!
   
   === Usage
  -You can see that what I put in the pom.xml is parametrized by some automatic Maven variables (they look like ${something}).
  -There is a residual parameter which is ${myimage.build} which in my case does not come from Maven internals, but from the command line: you can run the docker image generation like this:
  +You can see that what I put in the pom.xml is parametrized by some automatic Maven variables (they look like `${something}`).
  +There is a residual parameter which is `${myimage.build}` which in my case does not come from Maven internals, but from the command line: you can run the docker image generation like this:
   
   -------------------
   mvn docker:build -Dmyimage.build=12345
  
positive.code: 
  The biggest example of a docker registry is the official https://hub.docker.com/[Docker Hub] where lots of mainstream porjects publish their public images.
  
  Talk to your network administrator for all the concerns about it. You can also experiment by creating a Docker registry on your local machine while waiting for the IT guys to answer (it uusally takes some time :P ). More informations on the Docker registry can be found in the Docker guides.
  
  Second big point is, what kind of disk space on Artifactory do you have and what bandwidth availability. A well built Docker image should not require much more than a WAR/JAR artifact takes in terms of size and upload speed, but  this requires some tuning.
  
  
negative.code: You will see now how to produce the Docker image without needing any Dockerfile at all.
  
  === Configuration
  Let's see how to configure the plugin in the project's `pom.xml`: 
  
  [source, xml]
  -------------------
  