disk fill-up of Osmocombuild1, reasons

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Harald Welte laforge at gnumonks.org
Fri Oct 6 01:46:48 UTC 2017


Hi Neels,

On Thu, Oct 05, 2017 at 07:25:48PM +0200, Neels Hofmeyr wrote:
> Slave "build1-debian9-lxc" is running as lxc called 'docker'.
> /var/lib/lxc/docker/rootfs/var/lib/docker/vfs/dir contains 221G in 333 docker
> snapshots. It seems to me that these are growing indefinitely, that nothing is
> removing docker hashes that have been built. Does anyone have a discarding
> strategy ready that we can deploy there? We need to add one to avoid the build
> slave filling up again. https://osmocom.org/issues/2539

I updated the ticket.  Real fix is still pending.

> I also note that this lxc is not starting automatically after I rebooted
> Osmocombuild1 (to get rid of some stuck processes).
> I added
>   lxc.start.auto = 1
> to /var/lib/lxc/docker/config
> 
> Now the server is back up and running, the lxc is started, but the jenkins
> slave refuses to connect. It tries port 45 but nothing is listening
> there. I think I've hit this before but can't remember how to solve it :/
> https://osmocom.org/issues/2540

I updated that issue, and hopefully fixed it.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



More information about the OpenBSC mailing list