Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-3019

Testsuite: Docker controller leaves stray volumes and fills up disk space unnecessairly over time

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Migrated to another ITS
    • Affects Version/s: 5.8.1.Final
    • Fix Version/s: None
    • Component/s: Testing
    • Labels:
      None
    • Environment:

      Docker enabled Jenkins slaves

    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      docker volume prune

      Show
      docker volume prune

      Description

      Problem

      The Docker controller that allocates databases as Docker containers cleans up containers and does not leave unnecessary images:

      [root@karm-centos7-x86-64 ~]# docker images
      REPOSITORY           TAG                 IMAGE ID            CREATED             SIZE
      docker.io/postgres   9.4                 26bd9b04b948        6 days ago          232 MB
      docker.io/postgres   10                  0965cdc98045        6 days ago          234 MB
      docker.io/postgres   <none>              ed5db6e669ff        7 weeks ago         263 MB
      docker.io/postgres   <none>              30121e967865        7 weeks ago         289 MB
      [root@karm-centos7-x86-64 ~]# docker ps -a
      CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
      [root@karm-centos7-x86-64 ~]# 
      

      Although it leaves stray container volumes for some reason:

      [root@karm-centos7-x86-64 ~]# du -hs /var/lib/docker-latest/volumes
      15G	/var/lib/docker-latest/volumes
      [root@karm-centos7-x86-64 ~]# docker volume ls -qf dangling=true | wc -l
      409
      

      It unnecessarily clogs the slaves' disk space. The 15G of garbage has been created over dozens and dozens of builds with at least two containers each, but it shouldn't be happening anyway.

      Call to action

      Review whether removeContainerCmd is supposed to be enough to not only remove the container but to also remove its volume.

      Workaround

      docker volume prune
      

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                mbabacek Michal Karm
                Reporter:
                mbabacek Michal Karm
                Tester:
                Michal Karm
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: