Building a new docker image with the same name as an existing ones

If I build a new docker image with the same name as an existing ones, will the old ones be overwritten?

  • nginx/apache redirection for output port on docker container on vps
  • Relationship Between a Deis Cluster and Scale command?
  • How do I setup a read only private docker registry using just HTTP?
  • Docker - Network calls fail during image build on corporate network
  • how to run a daemon process in docker container with API/v1.5?
  • Node cannot join Swarm Cluster
  • Best way to stop Docker container in Jenkins
  • Difference b/w installing docker container using docker vs using marathon mesos
  • Why is virtualbox running so slowly under docker?
  • Is jwilder/nginx-proxy still actual since embedded DNS server in user-defined networks was introduced?
  • Handling database schema creation and migrations when launching multiple instances of a containerized microservice
  • Docker Registry vs Docker “Trusted” Registry
  • 2 Solutions collect form web for “Building a new docker image with the same name as an existing ones”

    Images in Docker don’t have a name, they have tags.

    A tag is a reference to an image. Multiple tags may refer to the same image.

    If you reassign a tag that is already used, then the original image will lose the tag, but will continue to exist (it will still be accessible by its image ID, and other tags might refer to it).

    You can use versions with your tags e/g/:

    docker build -t <USER>/<CONTAINER>:<VERSION>   
    docker build -t maluuba/haproxy:2
    docker build -t maluuba/haproxy:latest  #Default behavior when you don't use version
    docker build -t maluuba/haproxy:old
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.