Added as https://wiki.canonical.com/UbuntuEngineering/CI/Playbook#Destroying_old_containers
Thanks Francis. On 24 February 2014 22:45, Francis Ginther <[email protected]> wrote: > Evan, that was probably the best action. If there is no extra > containers to remove, then the only course I can think of is to clean > out the latest container's tmp files: > /var/lib/lxc/[lxc container name]/run/delta/tmp > > /tmp is where the temporary autopilot recordings are stored, which can > take up a big chunk of space. > > On Sat, Feb 22, 2014 at 7:29 AM, Evan Dandrea > <[email protected]> wrote: >> Nagios flipped out over the weekend when ps-nvidia-gt630 used up most >> of its disk. It looks like the trusty-amd64-20131210-1707 container >> was most to blame, as it was 150-200G. I dug around and it seems like >> otto only uses the most recent matching container (which this was >> not), so I destroyed it: >> >> ubuntu@ps-nvidia-gt630:~$ sudo lxc-destroy --name trusty-amd64-20131210-1707 >> >> We're now back down to 34% disk usage. >> >> If anyone sees this causing problems, please do let me know. Equally, >> if this was the right thing to do, I'd appreciate confirmation so I >> can get it in the playbook. >> >> Thanks! >> >> -- >> Mailing list: https://launchpad.net/~canonical-ci-engineering >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~canonical-ci-engineering >> More help : https://help.launchpad.net/ListHelp > > > > -- > Francis Ginther > Canonical - Ubuntu Engineering - Continuous Integration Team -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
