Closed MassiveBox closed 1 year ago
Sorry, I missed this previous issue which contains a solution: https://github.com/woodpecker-ci/woodpecker/issues/1457 This issue can be deleted. Thanks.
Check docker networks (docker network ls
) and delete unneeded ones. Looks like you have run out of available network address pool.
Alternative is to reconfigure and add additional network addresses to docker network address pool
With the push of this commit my pipeline started failing for no reason.
You can see in runs like this that not even the
clone
step is executed.I checked for logs and found these interesting things:
and, shortly after
I'm 100% certain that the pipeline didn't break because of errors in the config introduced in the latest push. I've re-run an old pipeline which worked, but now it fails.
I'm running the latest
next
inside Docker. Here's my docker-compose:I've tried rebooting, deleting and re-creating the containers with and without keeping the storage, and I can see that nothing seems to fix this issue. Please tell me how to further add information if necessary, thanks for your help!