# Apt-get update failing on Debian 8 (Jessie) based Convenience Images

**URL:** <https://discuss.circleci.com/t/apt-get-update-failing-on-debian-8-jessie-based-convenience-images/29257>\
**Category:** Build Environment\
**Created:** [March 26, 2019, 11:17am UTC](https://discuss.circleci.com/t/apt-get-update-failing-on-debian-8-jessie-based-convenience-images/29257 "2019-03-26T11:17:19Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![FelicianoTech](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/felicianotech/32/21348_2.png) [@FelicianoTech](https://discuss.circleci.com/u/FelicianoTech)\
**Post date:** [March 26, 2019, 11:17am UTC](https://discuss.circleci.com/t/apt-get-update-failing-on-debian-8-jessie-based-convenience-images/29257/1 "2019-03-26T11:17:20Z")

</div>

Hey everyone,

If you use a CircleCI Docker Convenience Image and you’re using a Debian Jessie based image, such as `circleci/php:7.1-jessie-browser`, `apt-get update` might be failing for you. You’ll see a 404 error on certain repository URLs.

This is because Debian 8 (Jessie) has been EOL’d by Debian and so they changed the mirrors. Here’s what happens now:

## Short-Term Solution

We’re working on getting the images restored to a working state. This should be done soon.

## Long-Term Solution

Debian 8 is EOL’d, meaning it’s no longer supported. Use a newer image tag. Depending on what image you are using, dropping the word `jessie` from your image tag will get you a Debian 9 (Stretch) based image. If that doesn’t work, typically you can replace the word `jessie` in your tag with `stretch`.

* * *

A summary of our images can be found [here](https://circleci.com/docs/2.0/circleci-images/) and a full list of our Docker images and their tags can be found [here](https://circleci.com/docs/2.0/docker-image-tags.json).

---

<div class="post-metadata">

**Author:** ![FelicianoTech](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/felicianotech/32/21348_2.png) [@FelicianoTech](https://discuss.circleci.com/u/FelicianoTech)\
**Post date:** [March 26, 2019, 3:13pm UTC](https://discuss.circleci.com/t/apt-get-update-failing-on-debian-8-jessie-based-convenience-images/29257/2 "2019-03-26T15:13:30Z")

</div>

Updated Jessie images are rolling out. It might take a little bit before hosts pick up the new images if they were cached.

Your best bet moving forward though is definitely to use non-Jessie based images as Debian has EOL’d the release.

---

<div class="post-metadata">

**Author:** ![thomasmost](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/thomasmost/32/21776_2.png) [@thomasmost](https://discuss.circleci.com/u/thomasmost)\
**Post date:** [March 26, 2019, 3:28pm UTC](https://discuss.circleci.com/t/apt-get-update-failing-on-debian-8-jessie-based-convenience-images/29257/3 "2019-03-26T15:28:11Z")

</div>

Hi, I’m a bit confused.

These are our current executors:

```
executors:
  default_executor:
    docker:
        - image: circleci/node:8.9.4
        - image: redis:2.8
        - image: circleci/mysql:5.6.35
    resource_class: medium+
  fe_executor:
    docker:
        - image: circleci/node:8.9.4
    resource_class: medium+

```

Where are we getting our Debian version from?

---

<div class="post-metadata">

**Author:** ![thomasmost](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/thomasmost/32/21776_2.png) [@thomasmost](https://discuss.circleci.com/u/thomasmost)\
**Post date:** [March 26, 2019, 3:47pm UTC](https://discuss.circleci.com/t/apt-get-update-failing-on-debian-8-jessie-based-convenience-images/29257/4 "2019-03-26T15:47:14Z")

</div>

@FelicianoTech do I need to update my `circleci/mysql` image?

---

<div class="post-metadata">

**Author:** ![vfn](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/vfn/32/411_2.png) [@vfn](https://discuss.circleci.com/u/vfn)\
**Post date:** [April 15, 2019, 11:10am UTC](https://discuss.circleci.com/t/apt-get-update-failing-on-debian-8-jessie-based-convenience-images/29257/5 "2019-04-15T11:10:10Z")

</div>

The base node image for `node:8.11.2` was defaulting to Debian jessie. I had to explicitly add `-stretch` suffix to the tag, for it to not use the jessie image.

Before:

```
docker:
  - image: circleci/node:8.11.2

```

After:

```
docker:
  - image: circleci/node:8.11.2-stretch
```

---

<div class="post-metadata">

**Author:** ![FelicianoTech](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/felicianotech/32/21348_2.png) [@FelicianoTech](https://discuss.circleci.com/u/FelicianoTech)\
**Post date:** [April 15, 2019, 1:44pm UTC](https://discuss.circleci.com/t/apt-get-update-failing-on-debian-8-jessie-based-convenience-images/29257/6 "2019-04-15T13:44:29Z")

</div>

Shouldn’t need to I don’t believe.

---

<div class="post-metadata">

**Author:** ![thomasmost](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/thomasmost/32/21776_2.png) [@thomasmost](https://discuss.circleci.com/u/thomasmost)\
**Post date:** [April 17, 2019, 2:11pm UTC](https://discuss.circleci.com/t/apt-get-update-failing-on-debian-8-jessie-based-convenience-images/29257/7 "2019-04-17T14:11:56Z")

</div>

Have the original Jessie images been fixed? Ideally we wouldn’t be using the ‘stretch’ images.

---

<div class="post-metadata">

**Author:** ![levlaz](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/levlaz/32/36978_2.png) [@levlaz](https://discuss.circleci.com/u/levlaz)\
**Post date:** [April 17, 2019, 3:46pm UTC](https://discuss.circleci.com/t/apt-get-update-failing-on-debian-8-jessie-based-convenience-images/29257/8 "2019-04-17T15:46:24Z")

</div>

> [@thomasmost](#):
>
> Ideally we wouldn’t be using the ‘stretch’ images.

Could you speak more to that? Strech is the latest stable release, jessie is now in LTS mode. Is there a specific reason why you want to stay on jessie?

---

<div class="post-metadata">

**Author:** ![thomasmost](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/thomasmost/32/21776_2.png) [@thomasmost](https://discuss.circleci.com/u/thomasmost)\
**Post date:** [April 17, 2019, 4:23pm UTC](https://discuss.circleci.com/t/apt-get-update-failing-on-debian-8-jessie-based-convenience-images/29257/9 "2019-04-17T16:23:07Z")

</div>

Well, it’s more similar to what we are using in production. Ideally, yes, we would update all our servers and workers, but in the meantime our CI should probably run on images close to what we’re using in prod.

---

<div class="post-metadata">

**Author:** ![levlaz](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/levlaz/32/36978_2.png) [@levlaz](https://discuss.circleci.com/u/levlaz)\
**Post date:** [April 17, 2019, 4:38pm UTC](https://discuss.circleci.com/t/apt-get-update-failing-on-debian-8-jessie-based-convenience-images/29257/10 "2019-04-17T16:38:20Z")

</div>

That makes sense, thanks for sharing your perspective!

---

<div class="post-metadata">

**Author:** ![thomasmost](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/thomasmost/32/21776_2.png) [@thomasmost](https://discuss.circleci.com/u/thomasmost)\
**Post date:** [April 17, 2019, 4:57pm UTC](https://discuss.circleci.com/t/apt-get-update-failing-on-debian-8-jessie-based-convenience-images/29257/11 "2019-04-17T16:57:38Z")

</div>

Thanks for listening!
