Dependency failing to download only in Docker image

nodejs
docker
#1

I am installing dependencies for a mobile app built in React Native and my build jobs have recently started failing this morning out of no where only on the android branch.

android-staging-release:
resource_class: large
working_directory: ~/project/android
docker:
  - image: circleci/android:api-27-node
steps:
  - checkout:
      path: ~/project
  - run: yarn

There is a post install script in our electron dependency that downloads a zip. This works fine on the iOS job running on macOS, but as of ~8 hours ago began failing with the output below.

I sshed into the machine and can use wget to download the zip file just fine. Is there something I’m missing about why a script to download a zip would respond with a 403 from the docker image, but not the mac machine?

error /home/circleci/project/node_modules/electron: Command failed.
Exit code: 1
Command: node install.js
Arguments: 
Directory: /home/circleci/project/node_modules/electron
Output:
/home/circleci/project/node_modules/electron/install.js:47
  throw err
  ^

Error: GET https://github.com/electron/electron/releases/download/v1.4.16/electron-v1.4.16-linux-x64.zip returned 403
    at Request.<anonymous> (/home/circleci/project/node_modules/nugget/index.js:169:61)
    at Request.emit (events.js:189:13)
    at Request.onRequestResponse (/home/circleci/project/node_modules/request/request.js:1068:10)
    at ClientRequest.emit (events.js:189:13)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:556:21)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:109:17)
    at TLSSocket.socketOnData (_http_client.js:442:20)
    at TLSSocket.emit (events.js:189:13)
    at addChunk (_stream_readable.js:284:12)
    at readableAddChunk (_stream_readable.js:265:11)
0 Likes

Issues fetching dependencies from Github
#2

We’re getting the same thing. But it’s not in a docker image. We can replicate it 100% of the time by running npm install react-devtools. This started happening on the morning of March 28

0 Likes

#3

it’s working now… an update from the circleci team would be nice…

0 Likes

#4

Do you mean from your local computer?

0 Likes

#5

Sorry for the delay in responding. We believe this was caused by some silent rate limiting on GitHub, but we can’t confirm. Glad to hear it is fixed.

0 Likes

closed #6

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

0 Likes