CODEWITHSUNDEEP
dockerdocker-composedebiandebian-buster
EmilyD
EmilyD

Reputation: 75

My docker filesystem duplicates itself for no reason

My FS has been filled by my docker container (docker pull dependencytrack/apiserver). It seems it has duplicated itself in many subfolders.

find /var/lib/docker/overlay2/ -name alpine-1.10.2.jar | wc -l
1550

(answer should be closer to 1, I guess).

They all reside in /var/lib/docker/overlay2/[diff|merged]/<random_number1>/tmp/jetty-0_0_0_0-8080-dependency-track-apiserver_jar-dtrack-api-any-<random_number2>/webapp/WEB-INF/lib/

where random_number1 is fixed and random_number2 has many differents values.

Is this problem related to my image, or is it docker ? I don't really know how to proceed from here.

Upvotes: 1

Views: 320

Answers (1)

Alexander Nikiforov
Alexander Nikiforov

Reputation: 64

for me a simple redeployment of docker container in which dependency track is used helped.

I think that dependency server backend application lies in /tmp folder of your docker container.

If your container is healthy, then you will see only one such jetty container in /tmp folder inside Docker container.

If something goes wrong, it replicates jetty servers over and over again in /tmp folder, thus polluting it.

In dependency track Dockerfile should be implemented "HEALTHCHECK", so you might want to monitor that. If your container is unhealthy, then you might want to redeploy your container or see what is going on to fix the problem.

That does not of course pin point the reason of error, which only can be traced if you analyse the logs of Docker container in which dependency track runs.

But this hopefully can help to solve the problem.

Upvotes: 0

Related Questions