Bug #4839
closed
docker.io sometimes returns EOF, breaking our builds
Added by laforge over 3 years ago.
Updated over 3 years ago.
Description
We have plenty of situations where docker.io seemingly returns EOF (i.e. nothing) when pulling a base image like debian:stretch
. The failure to pull will cause our jenkins job (e.g. a TTCN3 test) to fail, despite no failure on our side.
This has appeared even before docker introduced rate limiting today, so it is unrelated to that.
- Status changed from New to In Progress
- % Done changed from 0 to 10
- Status changed from In Progress to Resolved
- % Done changed from 10 to 100
Related patches all merged, hopefully those problems are now gone.
I've manually verified that the registry-update-base-images job works, and also executed ttcn3-stp-test once to see if it actually pulls from registry.osmocom.org now.
- Related to Feature #4840: migrate osmo-gsm-tester docker images to registry.osmocom.org added
And of course, on day 1 of this new mechansim, we see:
while all other builds succeed, using base images from registry.osmocom.org.
yay.
- Related to Bug #4850: ttcn3-gbproxy-test* are not generated by jenkins-job-builder added
Also available in: Atom
PDF