Docker images -a showing several images with repository <none>

When I use command docker ps -a it lists several images with repository <none>. I’m assuming they’re related to another image given the similar time stamp. I’m just wondering what their purpose is?

REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
opensuse            latest              33ab078b606b        5 days ago          254.6 MB
mattgruter/drone    latest              ec2ee19cb579        2 weeks ago         312.4 MB
<none>              <none>              69d95bd4b1f9        2 weeks ago         312.4 MB
<none>              <none>              227d0f1e0dfa        2 weeks ago         312.4 MB
<none>              <none>              a19dbed68faa        2 weeks ago         312.4 MB
<none>              <none>              01ff591e80dc        2 weeks ago         312.4 MB
<none>              <none>              89c0c546d2ba        2 weeks ago         312.4 MB
<none>              <none>              030d18544ee4        2 weeks ago         279.1 MB
<none>              <none>              1aaa2da8e8c2        2 weeks ago         271.6 MB
<none>              <none>              c7928e43d1b3        2 weeks ago         269.9 MB
<none>              <none>              0252973e04f0        2 weeks ago         268.6 MB
<none>              <none>              2004ab1a6ca0        2 weeks ago         268.6 MB
<none>              <none>              c26aae018d13        2 weeks ago         268.6 MB
<none>              <none>              5707a16ae741        2 weeks ago         268.6 MB
<none>              <none>              d959a0f0afef        2 weeks ago         268.6 MB
<none>              <none>              bd654a62529d        2 weeks ago         268.6 MB
<none>              <none>              bd52fe5f72a3        2 weeks ago         220.6 MB
<none>              <none>              cd074038dbb7        2 weeks ago         209.2 MB
<none>              <none>              4c12a68b82b3        2 weeks ago         188.3 MB
<none>              <none>              f272e06028fd        2 weeks ago         188.3 MB
<none>              <none>              6d4946999d4f        3 weeks ago         188.3 MB
<none>              <none>              9fd3c8c9af32        3 weeks ago         188.3 MB
<none>              <none>              435050075b3f        3 weeks ago         188.3 MB
<none>              <none>              428b411c28f0        3 weeks ago         188.1 MB
<none>              <none>              5b8dd08af89b        10 weeks ago        0 B

  • Concourse cant put docker image to local repo, not a vaild repository/tag
  • Execute docker commands in jenkins (in docker container)
  • pushing docker image to dockerhub
  • How to use multiple base images to build a docker image
  • Getting cron to run on php:7-fpm image [closed]
  • coreos docker 1.7.1 -v file.txt:file.txt not updating
  • How to prevent zombie services with consul and gliderlabs/registrator?
  • How to configure NGINX routes?
  • port redirect to docker containers by hostname
  • C source files not allowed when not using cgo or SWIG: sqlite3-binding.c
  • Run Docker PHP-apache: Forbidden You don't have permission to access / on this server
  • Gitlab & Mattermost OAUTH Time out
  • One Solution collect form web for “Docker images -a showing several images with repository <none>”

    When you build an image docker creates temporary container to move from one step to another.
    However these “< none >” images are something else; they are created when you build an image with the same repository/tag as one that has already been pulled. They are called dangling/untagged images.
    You can clean them up via:

    docker rmi $(docker images -f "dangling=true" -q)
    
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.