What you’re suggesting doesn’t mirror the behavior I’m seeing from docker-compose, but there’s more below regarding my supposition. The docker-compose command most certainly seems to run in an automated way, either because of the way the Docker container was originally defined or because of some internal synchronization / retry system.
As I said, I’m new to Docker. Thus, I don’t know what setups are possible within containers. I also had no hand in building the container nor the deployment of it. I’m stepping in much later to review an already built and operating container (4 of them, actually).
What I’ve come to find is a large tar file is being built in the /tmp directory at random, but regular intervals. I stepped through standard SA file determination steps (using ‘file’ and ‘lsof’) on that temporary file and have uncovered docker-compose at the heart this tar file build. I understand that the docker-compose command can be used for backup and restoration manually, but that’s not what seems to be occurring on this system. I’ve spoken to the developer of the container and he has not mentioned launching such backup / restore activity. However, I might not have all of the necessary information here after-the-fact.
It seems that whatever way each container is built is somehow causing docker-compose to produce temporary tar files in /tmp… as I said, regularly. Though, I believe this process may also be failing because /tmp is too small and it’s running the volume out of space.
With that said, it’s possible that a docker-compose command was originally issued manually at some point in the past and because /tmp is being run out of space, it is continuing to retry this request infinitely and failing every time. To me and because I’m coming into this late, it looks like an automated process and, in a way, is automated if it is retrying infinitely. I also have no idea how to cancel it, if so.
Though, I am certain that it is docker-compose creating (and possibly failing to create) this tar file in an automated way. Whether that “automation” is because it’s failing and then retrying, I have no way to easily know this.
The whole reason this has become a problem is that when this docker-compose process runs, it also runs the /tmp volume out of space. This, in turn, affects another Docker container’s software which doesn’t recover from this out-of-space condition without restarting (a separate bug report for another product).
Yes, there are other issues surrounding the volumes built in the operating system that also need to be addressed to prevent such future issues, but docker-compose is compounding this issue because I’ve no way to know the reason why it continually keeps running this tar file build or how to cancel the operation… or even better, how to redirect this build operation to a separate volume with more space.
If you have any other ideas, please let me know.