#3014 closed task (fixed)

woodie builds fail due to exceeded quota

Reported by: strk Owned by: robe
Priority: normal Milestone: Sysadmin Contract 2023-I
Component: SysAdmin/Woodie Keywords:
Cc:

Description

Especially when we have many steps, where each step creates a container, it's easy to end up out of space.

This pull request for woodpecker-ci should help with this problem: https://github.com/woodpecker-ci/woodpecker/pull/2681

Meanwhile our best chance is to docker system prune as often as possible.

Change History (4)

comment:1 by strk, 13 months ago

Component: SysAdminSysAdmin/Woodie
Owner: changed from sac@… to robe

comment:2 by robe, 13 months ago

Milestone: UnplannedSysadmin Contract 2023-I

I thought I did do a daily docker system prune on woodie-server and all the woodie-client

It only runs daily though.

If I'm already doing that, I can up the space available on them. I think I had made it a modest 150G or so.

comment:3 by strk, 13 months ago

How about hourly instead of daily ?

comment:4 by robe, 13 months ago

Resolution: fixed
Status: newclosed

We could do that, but ultimately I think the issue is docker system prune is not pruning everything. Even after doing

docker system prune --all --force

There still seem to be large numbers of orphan /var/lib/docker/vfs left around amounting to about 60 GB still left. I ended up just reinitializing all of them with the base image or snapshot from osgeo8 woodie-client/reset

This is safe to do with the clients since I think the logs are kept on woodie-server, so nothing is lost.

I do plan to try podman to see if it does a better job of cleaning up when you ask it to clean up.

The reset image ends up creating a container with 1.4 GB in use (which includes the woodie client running, but no images beside the woodpecker one)

Note: See TracTickets for help on using tickets.