# Sudo apt-get update returned exit code 100 on ubuntu builds within circle **URL:** \ **Category:** Build Environment\ **Created:** [July 24, 2018, 8:25pm UTC](https://discuss.circleci.com/t/sudo-apt-get-update-returned-exit-code-100-on-ubuntu-builds-within-circle/23807 "2018-07-24T20:25:58Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![JenWardell](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/jenwardell/32/13079_2.png) [@JenWardell](https://discuss.circleci.com/u/JenWardell)\ **Post date:** [July 24, 2018, 8:25pm UTC](https://discuss.circleci.com/t/sudo-apt-get-update-returned-exit-code-100-on-ubuntu-builds-within-circle/23807/1 "2018-07-24T20:25:58Z")
Hi there, I’m getting sudo apt-get update returned exit code 100 on running that command as part of the build environment using ubuntu 16 More info: Fetched 3,972 kB in 2min 29s (26.5 kB/s) W: Size of file /var/lib/apt/lists/security.ubuntu.com\_ubuntu\_dists\_trusty-security\_multiverse\_binary-amd64\_Packages.gz is not what the server reported 4727 4728 W: Size of file /var/lib/apt/lists/cli-assets.heroku.com\_branches\_stable\_apt\_.\_Packages.gz is not what the server reported 562 760 W: Size of file /var/lib/apt/lists/archive.ubuntu.com\_ubuntu\_dists\_trusty-updates\_multiverse\_binary-amd64\_Packages.gz is not what the server reported 16013 16331 W: Failed to fetch copy:/var/lib/apt/lists/partial/packagecloud.io\_circleci\_trusty\_ubuntu\_dists\_trusty\_main\_source\_Sources Failed to stat - stat (2: No such file or directory) W: Failed to fetch copy:/var/lib/apt/lists/partial/packagecloud.io\_github\_git-lfs\_ubuntu\_dists\_trusty\_main\_source\_Sources Failed to stat - stat (2: No such file or directory) E: Some index files failed to download. They have been ignored, or old ones used instead. No changes have been made to the build flow, and this has only happened today on commits. ---
**Author:** ![halfer](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/halfer/32/9083_2.png) [@halfer](https://discuss.circleci.com/u/halfer)\ **Post date:** [July 24, 2018, 8:37pm UTC](https://discuss.circleci.com/t/sudo-apt-get-update-returned-exit-code-100-on-ubuntu-builds-within-circle/23807/2 "2018-07-24T20:37:06Z")
What base Docker image are you using? ---
**Author:** ![JenWardell](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/jenwardell/32/13079_2.png) [@JenWardell](https://discuss.circleci.com/u/JenWardell)\ **Post date:** [July 24, 2018, 8:51pm UTC](https://discuss.circleci.com/t/sudo-apt-get-update-returned-exit-code-100-on-ubuntu-builds-within-circle/23807/3 "2018-07-24T20:51:03Z")
Hilariously as soon as I posted this the builds started going through again. It might have been an issue they just resolved, or it could have been something on trusty side. Funny though as it’d been going on for an hour or so lol. ---
**Author:** ![halfer](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/halfer/32/9083_2.png) [@halfer](https://discuss.circleci.com/u/halfer)\ **Post date:** [July 25, 2018, 7:38am UTC](https://discuss.circleci.com/t/sudo-apt-get-update-returned-exit-code-100-on-ubuntu-builds-within-circle/23807/4 "2018-07-25T07:38:44Z")
It’s a reverse Schroedingbug - as soon as you post a fault report, It Knows and starts working again. Computers do like a chuckle! ---
**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\ **Post date:** [October 23, 2018, 7:39am UTC](https://discuss.circleci.com/t/sudo-apt-get-update-returned-exit-code-100-on-ubuntu-builds-within-circle/23807/5 "2018-10-23T07:39:06Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.