Apt-get update return 404

Build Environment
21

Hi, could you please help?
We’re using a machine executor and it worked fine, but today it started failing with next error:
E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists/
Exited with code 100

22

Please search for that error on the forum, it is being discussed on other recent threads. It is largely unrelated to the Ubuntu outage.

23

Hi, sorry I’m getting the
Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found

error also.
Admittedly all this confuses me, do I need to update my circleci config.yml? How do I do that?

I’m using:

version: 2.1

orbs:
  cypress: cypress-io/cypress@1.0.0

jobs:
  build:
    docker:
      - image: circleci/node:8.10
.....

Sorry! Just noticed:

24

After adding these lines it errors

This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package libgconf-2-4 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libxi6' has no installation candidate
E: Package 'libgconf-2-4' has no installation candidate
Exited with code 100

My Config file looks like this

  build:
    docker:
      - image: circleci/ruby:2.3.4
      - image: selenium/standalone-chrome:latest
      - image: circleci/mysql:5.7.18
    working_directory: ~/repo
    steps:
      - checkout
      - run: echo "Running from .circleci/config.yml"
      - run: echo $CC_TEST_REPORTER_ID
      - run: ruby -v
  - run:
          name: Install latest version of Chrome
          command: |
            sudo rm /etc/apt/sources.list
            echo "deb http://archive.debian.org/debian/ jessie-backports main" | sudo tee -a /etc/apt/sources.list
            echo "deb-src http://archive.debian.org/debian/ jessie-backports main" | sudo tee -a /etc/apt/sources.list
            echo "Acquire::Check-Valid-Until false;" | sudo tee -a /etc/apt/apt.conf.d/10-nocheckvalid
            echo 'Package: *\nPin: origin "archive.debian.org"\nPin-Priority: 500' | sudo tee -a /etc/apt/preferences.d/10-archive-pin
            sudo apt-get update
            sudo apt-get install -y unzip xvfb libxi6 libgconf-2-4
            sudo wget -q https://dl-ssl.google.com/linux/linux_signing_key.pub -O- | sudo apt-key add -
            sudo su -c 'echo "deb http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google-chrome.list'
            sudo apt-get -y update
            sudo apt-get -y install google-chrome-stable
25

Yes, I got that on Tuesday too - I was wanting to fix up a PHP 5.4 image based on Jessie, and after repairing it in the way that you did, it seemed to get its OS updates (via apt-get upgrade) but then simple tools (like wget) would not install.

In the end I built a new Docker image and compiled PHP 5.4 from scratch. A bit of a fiddle, but it’s nice to be on a supported operating system.

It’s possible that the Jessie image is fully repairable - it has only been archived as far as I can tell - but I was not willing to spend more time on it. I estimated that it was quicker to fix the issue properly (move off Jessie) that spend time debugging Apt.

26

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.