I am using circleci/ruby:2.2.10-node #!/bin/bash -eo pipefail sudo apt-get update Ign http://http.us.debian.org jessie-backports InRelease Ign http://http.us.debian.org jessie-backports Release.gpg Ign http://http.us.debian.org jessie-backports Release Err http://http.us.debian.org jessie-backpo…

I ended up adding the following lines to my config.yml: sudo sed -i '/jessie-backports/d' /etc/apt/sources.list sudo sed -i '/jessie-updates/d' /etc/apt/sources.list ZZ

I’m seeing the same with circleci/node:10.12.0.

Looks like it could be an issue with debian mirrors, though it’s hard to tell which one. [image] Issue: "sudo apt-get update" failing on default images opened by kevinburke on 2018-10-22 closed by ryanwohara on 2018-10-23 Running “docker run -it --rm circleci/node:10-bro…

Still error, FYI there aren’t any circleci/ruby:2.2.10-stretch-node ====>> Update Chromedriver #!/bin/bash -eo pipefail wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add - sudo sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /et…

Can someone from the CircleCI team please post an update on when can a Ruby:2.2.x image based on Debian Stretch will be available or alternatively change the mirrors in the current Ruby:2.2-node that’s based on Debian Jessie?

Ruby is not being maintained upstream https://hub.docker.com/_/ruby Therefore we will not be updating it. 2.3-stretch-node-browsers-legacy is the oldest tag currently, and it has been updated. If you need to use 2.2 and can not make your own image, you can add the changes from Apt-get update retur…

@drazisil , kindly excuse my typo as I meant circleci/ruby:2.2.x based on Debian stretch instead of plain ruby & thanks for letting us know stretch versions are available only since ruby-2.3 Will look to implement the suggested workaround & post here regardless of success / failure so that it’ll hel…

Ah, no, I was unclear. What I meant was that we only update images that are maintained upstream, and since Ruby is not updating 2.2, CircleCI will not be updating any of our 2.2 tags as well. So, yes, you will need to update to 2.3. Hopefully, this works for you, I look forward to your results …

@zeninfinity as a hot-fix, that worked for me too compared to the more elaborate changes mentioned by @drazisil , cheers guys :+1:

CircleCI failing when using sudo apt-get update

Build Environment

drazisil March 27, 2019, 1:14pm 4

This was covered here Apt-get update failing on Debian 8 (Jessie) based Convenience Images

Topic		Replies	Views
"sudo apt-get update" is failing with default CircleCI Docker images Feedback & Bug Reports	4	3175	October 23, 2018
Apt-get update return 404 Build Environment circle-yml	24	12653	April 4, 2019
RUN apt-get update is failing on the Circle CI docker image Build Environment	1	2549	March 26, 2019
Failed to fetch Debian Feedback & Bug Reports	2	7239	March 26, 2019
Apt-get update fails only on some containers, but works on others? Feedback & Bug Reports	5	1224	January 31, 2019

CircleCI failing when using sudo apt-get update

Related topics