I’m new to Docker and are currently evaluating it’s use in order to integrate it in our CI, doing automated integration test during builds.
I just set up a private registry but I also realized that when working with images we store on that private registry we always have to use the full image name containing the url + port number (when pulling but also when referencing a parent image with a Dockerfile FROM).
Is this really the only way to work or is there some configuration of docker to define the location of some named registry?
For me this is a choose stopper, I can’t imagine that I build 100s of Dockerfile that all depends on the URL + port of my registry.
What if at some point it moves?
Also it is impossible for us to use only Docker HUB, we are a company and some of the content of the images can’t simply be outside of our company.
I would imagine that naming of image would go something like my_registry_name/my_project_name/my_image_name then being able to configure docker to define the URL+port of my registry : my_registry_name -> my.server.mydomain:1234
I come from the Java world and would really appreciate something similar to the way maven works.
What are the possible workaround? Is Docker planning to change the way it works?