Both apt-get calls in the Dockerfile, apt-get update and apt-get install, now pass -o Acquire::Retries=5, so a download that Ubuntu's snapshot service fails with a brief 503 is retried for about half a minute before the build gives up. The snapshot date, the hash check of the InRelease files and the rest of the step are unchanged. One added sentence in the step's comment says why the option is there.
Deviation from the issue's premise: apt in the pinned Ubuntu image (apt 3.2.0) already retries a 503 three times by default, waiting 1, 2 and 4 seconds, so the change raises retries from three to five, which wait 8 and 16 seconds more, rather than from none.
Judgement call: five, as the issue suggests. A 503 outage longer than about 31 seconds still fails the build.
No automated test: a 503 from the snapshot service cannot be produced on demand, and a test that reads the Dockerfile for the option would check the file rather than the behaviour.
Partly verified: the five retries were seen by hand in the pinned Ubuntu image against a source that refuses connections, not against a real 503; apt's source treats both as worth retrying.
Model: opus-5-5
Both `apt-get` calls in the `Dockerfile`, `apt-get update` and `apt-get install`, now pass `-o Acquire::Retries=5`, so a download that Ubuntu's snapshot service fails with a brief 503 is retried for about half a minute before the build gives up. The snapshot date, the hash check of the `InRelease` files and the rest of the step are unchanged. One added sentence in the step's comment says why the option is there.
- Deviation from the issue's premise: apt in the pinned Ubuntu image (apt 3.2.0) already retries a 503 three times by default, waiting 1, 2 and 4 seconds, so the change raises retries from three to five, which wait 8 and 16 seconds more, rather than from none.
- Judgement call: five, as the issue suggests. A 503 outage longer than about 31 seconds still fails the build.
- No automated test: a 503 from the snapshot service cannot be produced on demand, and a test that reads the `Dockerfile` for the option would check the file rather than the behaviour.
- Partly verified: the five retries were seen by hand in the pinned Ubuntu image against a source that refuses connections, not against a real 503; apt's source treats both as worth retrying.
Model: opus-5-5
Both apt-get calls in the Dockerfile now pass -o Acquire::Retries=5.
apt already retries a download that fails with 503 three times,
waiting 1, 2 and 4 seconds, which a short outage of the snapshot
service outlasted; five retries wait about half a minute in all.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Both
apt-getcalls in theDockerfile,apt-get updateandapt-get install, now pass-o Acquire::Retries=5, so a download that Ubuntu's snapshot service fails with a brief 503 is retried for about half a minute before the build gives up. The snapshot date, the hash check of theInReleasefiles and the rest of the step are unchanged. One added sentence in the step's comment says why the option is there.Dockerfilefor the option would check the file rather than the behaviour.Model: opus-5-5
PASS
Model: opus-5-5