<registry>registry.hub.docker.com:443</registry>
<image>
<alias>base-web</alias>
<name>base-web</name>
<!-- https://registry.hub.docker.com/repos/<my username> is resolvable -->
<registry>registry.hub.docker.com:443</registry>
<build>
<assembly>
<dockerFileDir>base-web</dockerFileDir>
</assembly>
</build>
Do you mean your personal account on DockerHub (the public registry) ?
If so, then you dont need to configure any extra registry, since this is
the default.
> I have tried an auth setting using properties, <authConfig> and
Indeed you need to authenticate with your DockerHub account's
credentials. The recommended way is to do this in your
~/.m2/settings.xml as described in
http://fabric8io.github.io/docker-maven-plugin/authentication.html
For a first check -Ddocker.username=... -Ddocker.password=... on the
command line would do, too.
> It is not clear to me what the relationship is between docker.io and
> dockerhub, or what the URL scheme is behind personal / org scoped
> Dockerhub repositories.
Your account needs to be configured as the user part of the image name.
So, in your example you want an image "base-web" and your account is
"ben" then you should use a <name>ben/base-web</name> in the configuration.
In general, the image name is "registry/user/image-name:tag", however
the registry part can be omitted when talking to DockerHub or when using
the <registry>private-registry</registry> part.
[INFO] DOCKER> ... The push refers to a repository [docker.io/bendg25/base-web]
[ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.14.2:push (default-cli) on project docker: Unable to push 'bendg25/base-web': Repository does not exist: bendg25/base-web -> [Help 1]