Дата публикации: 04-05-2026 21:15:13

Ubuntu’s status shows as Ok now, however, on highly parallel jobs, I’m still seeing some lingering slowness updating / installing packages from apt. Is it possible they’ve implemented some additional rate-limiting which is affecting CircleCI when a lot of requests are coming from a small number of nodes?
Also, a note, in case it’s helpful to others: using apt-get can cause indefinite hanging on certain types of timeouts that seems to ignore no_output_timeout. I talked to support, and, after some back and forth, they suggested that apt-get is rewriting the same line by default, and to add -q to the options for apt-get, which should suppress that behavior.
https://support.circleci.com/hc/en-us/articles/37474192881179-Resolving-Unable-to-connect-to-archive-ubuntu-com-403-Forbidden-Error-in-CircleCI
that’s not mentioned here, so figured I’d mention it in case it helps others.
I did also add a variation on this, to setup some caching.




Caching apt-get packages Community



Many of you have asked about caching apt-get installs.
I’m here to tell you that there’s a way!
Basically it involves downloading the apt packages and caching that directory between builds.
Additionally, I will show you how to use a custom sources.list to speed up apt-get update for your builds.
A full example
We’ll start out with a full, commented, example and then walk through the what and why after.
dependencies:
cache_directories:
# We will store packages in this directory
- "…

1 post - 1 participant
Read full topic

Основное содержимое страницы с новостью.

Схожие новости