Overlay volumes are out of control #928
Comments
I can't think of a reason that RancherOS would behave differently than any other distro here. If you do see different results on Ubuntu though, we'll definitely look into this! |
I have tested it on Ubuntu, and the issue is not present. My other thought would be Storage Driver differences, since rancherOS is |
Currently having the same issue. Not sure if it is related to |
I have also seen huge lists making df unusable, I've not done any testing towards what causes it though |
Is there a workaround for this? I awoke this morning to many downed services (that have been working fine for months) and discovered all hosts were out of disk space. There are thousands of these entries in /var/lib/docker/overlay. I'd like to figure out how to fix it quickly vs, re-deploying new hosts and updating DNS. |
@JacieChao |
We could set overlay2 for both system-docker and user docker as storage driver. According to my verification,this issue can be mitigated by using overlay2. The verify steps are as follows:
As the result, using overlay2 as storage driver can save almost 10% storage, and the storage growth was not obvious when upgrading the container. In my test, When running |
Close it. |
What's the proper way to fix this? |
When running
sudo df
logged in asrancher
via ssh, I get 2000+ entities such as this:They're all the same folder, but once in a while the size changes.
Tracking it down, its a container than I start on a schedule using rancher-cron (something I am working on as a simple cron solution) once a minute. The container itself is set to
io.rancher.container.start_once=true
and maintained byrancher
.Output of
docker inspect
:output of
docker info
:This also spun
t2.small
instance out of control (not entirely sure as there were other services on that machine), leading to 30+ load, with very minimal actual usage, filled with lines like:As soon as the box had containers removed from it, it stopped having load problems.
I am now re-running everything using an Ubuntu 14.04 instance to see if the issue is with RancherOS or not.
Unfortunately, before I figured that its a good idea to open this issue, I have terminated the box, so I cannot pull any additional from the instance.
RancherOS Version: 0.4.4
Where are you running RancherOS? AWS
The text was updated successfully, but these errors were encountered: