How do I define the name of image built with docker-compose

Question

I m using docker-compose to create my development environment  I want to build a specific image  but I don t know how to set a name for that image   wildfly    build   path to dir Dockerfile   container name  wildfly server   ports     - 9990 9990    - 80 8080   environment     - MYSQL HOST mysql server    - MONGO HOST mongo server    - ELASTIC HOST elasticsearch server   volumes     -  Volumes CaseSensitive development wildfly deployments   opt jboss wildfly standalone deployments    links     - mysql mysql server    - mongo mongo server    - elasticsearch elasticsearch server   When I execute docker-compose everything is ok  but I get a random name for the new image  Is it possible to set a name to the build image

User · Answer

According to 3 9 version of Docker compose  you can use image  myapp tag to specify name and tag  version   quot 3 9 quot  services    webapp      build        context          dockerfile  Dockerfile     image  webapp tag  Reference  https   docs docker com compose compose-file compose-file-v3

User · Answer

Depending on your use case  you can use an image which has already been created and specify it s name in docker-compose    We have a production use case where our CI server builds a named Docker image   docker build -t  lt specific image name gt      Once the named image is specified  our docker-compose always builds off of the specific image  This allows a couple of different possibilities   1- You can ensure that where ever you run your docker-compose from  you will always be using the latest version of that specific image   2- You can specify multiple named images in your docker-compose file and let them be auto-wired through the previous build step   So  if your image is already built  you can name the image with docker-compose  Remove build and specify image   wildfly    image  my custom wildfly image   container name  wildfly server   ports     - 9990 9990    - 80 8080   environment     - MYSQL HOST mysql server    - MONGO HOST mongo server    - ELASTIC HOST elasticsearch server   volumes     -  Volumes CaseSensitive development wildfly deployments   opt jboss wildfly standalone deployments    links     - mysql mysql server    - mongo mongo server    - elasticsearch elasticsearch server

User · Answer

after you build your image do the following   docker tag  lt image id gt  mynewtag version  after that you will see your image is no longer named  lt none gt  when you go docker images

User · Answer

As per docker-compose 1 6 0      You can now specify both a build and an image key if you re using the new file format  docker-compose build will build the image and tag it  with the name you ve specified  while docker-compose pull will attempt to pull it    So your docker-compose yml would be  version   2  services    wildfly        build   path to dir Dockerfile       image  wildfly server       ports         - 9990 9990        - 80 8080   To update docker-compose  sudo pip install -U docker-compose  1 6 0

User · Answer

For docker-compose version 2 file format  you can build and tag an image for one service and then use that same built image for another service  For my case  I want to set up an elasticsearch cluster with 2 nodes  they both need to use the same image  but configured to run differently   I also want to build my own custom elasticsearch image from my own Dockerfile   So this is what I did  docker-compose yml   version   2   services    es-master      build    elasticsearch     image  porter elasticsearch     ports        -  quot 9200 9200 quot      container name  es master    es-node      image  porter elasticsearch     depends on        - es-master     ports        -  quot 9200 quot      command  elasticsearch --discovery zen ping unicast hosts es master  You can see that in the first service definition es-master  I use the build option to build an image from the Dockerfile in   elasticsearch   I tag the image with the name porter elasticsearch with the image option  Then  I reference this built image in the es-node service definition with the image option  and also use a depends on to make sure the other container es-master is built and run first

User · Answer

Option 1  Hinting default image name  The name of the image generated by docker-compose depends on the folder name by default but you can override it by using --project-name argument     docker-compose --project-name foo build bar   docker images foo bar   Option 2  Specifying image name  Once docker-compose 1 6 0 is out  you may specify build  and image  to have an explicit image name  see arulraj net s answer    Option 3  Create image from container  A third is to create an image from the container     docker-compose up -d bar   docker commit   docker-compose ps -q bar  foo bar   docker-compose rm -f bar

[docker] How do I define the name of image built with docker-compose

Examples related to docker

Examples related to docker-compose

Examples related to orchestration