4

here is my docker-compose file

and I built the image with docker-compose build command.

How can I build the named images ? Because I got too many nonamed images

DOCKERFILE

    FROM rails:onbuild
    # RUN apt-get update -qq && apt-get install -y build-essential libpq-dev
    RUN apt-get update && apt-get -y upgrade
    RUN apt-get -y -qq --force-yes install \
            build-essential \
            tree \
            ruby-dev \
            vim \
            vim-scripts \
            git \
            git-flow\
            curl \
            zsh \
            sudo


# Install Zsh
################## BEGIN INSTALLATION ######################
RUN git clone git://github.com/robbyrussell/oh-my-zsh.git ~/.oh-my-zsh \
      && cp ~/.oh-my-zsh/templates/zshrc.zsh-template ~/.zshrc \
      && chsh -s /bin/zsh

docker-compose.yml

db:
  image: postgres
  ports:
    - "5432"
web:
  build: .
  command: bundle exec rails s -p 3001 -b '0.0.0.0'
  volumes:
    - .:/associated-press
  ports:
    - "3001:3001"
  links:
    - db

Too many noname images

associated_press git:(master) ✗ docker images                                                                                                                 (master⚡)
REPOSITORY               TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
<none>                   <none>              80c216ddb2a7        About an hour ago   1.093 GB
<none>                   <none>              115a747757ec        About an hour ago   1.065 GB
associatedpress_web      latest              cf136ac96689        About an hour ago   1.185 GB
<none>                   <none>              c3e538c87495        17 hours ago        1.185 GB
<none>                   <none>              c41d47cc6647        17 hours ago        1.185 GB
<none>                   <none>              cd57f0d2165f        17 hours ago        1.185 GB
<none>                   <none>              64544f8cb188        17 hours ago        1.185 GB
<none>                   <none>              afd369c991d1        17 hours ago        1.185 GB
<none>                   <none>              54113a645b47        19 hours ago        1.184 GB
<none>                   <none>              d6986f926c4a        19 hours ago        1.184 GB
<none>                   <none>              a22979b350af        19 hours ago        1.184 GB
<none>                   <none>              5efecb684ecd        19 hours ago        1.064 GB
<none>                   <none>              fca65cdaecfc        19 hours ago        1.184 GB
<none>                   <none>              bf6ff095eedb        19 hours ago        1.064 GB
<none>                   <none>              0697417f2fd1        19 hours ago        1.064 GB
<none>                   <none>              9ed0d5b6fc70        19 hours ago        1.064 GB
<none>                   <none>              f883183e0870        20 hours ago        1.161 GB
<none>                   <none>              caa221a5f56e        20 hours ago        1.161 GB
<none>                   <none>              88e6c706176f        20 hours ago        1.064 GB
<none>                   <none>              3b48ab1152f4        20 hours ago        1.064 GB

1 Answer 1

3

I'm not aware of a way to set a custom name for images, compose always tags the images as project_service:latest. A pattern we've used is startup scripts similar to this:

#!/bin/sh
docker-compose kill
docker-compose rm --force -v
docker rmi project_service:latest    # prevents buildup of untagged images
docker-compose build
docker-compose up -d

If you don't want to use a startup script, another solution is to keep this handy and run it frequently:

docker rmi $(docker images -q -f dangling=true)
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.