1
Step #0: [2/4] Fetching packages...    
Step #0: info There appears to be trouble with your network connection. Retrying...

The retrying step happens X times until I cancel. It worked once after 457s, but failed because this also happens inside docker containers, and there it is a timeout.

Anyone else experiencing this?

Think it is a network bug from Google. Started experiencing this today.

Does not happen locally.

vonGohren
  • 111
  • 3

4 Answers4

1

npm registry was having a connection problem at 10.28 UTC.

mforsetti
  • 2,666
  • 2
  • 16
  • 20
1
“But it would be great with an issue tracker of some sorts? 
 Or a status page if anyone knows about it?”

Yes, visit here to check status information on the services that are part of Google Cloud.
For third party softwares like NPM, you can check their respective status pages, for example - this for NPM. Subsequently, you can also check build logs, the next time you face an anomaly with Cloud Build..

Anant Swaraj
  • 169
  • 4
  • Thanks alot for these status pages! I did watch the build logs and they were just saying network error or slowness. But I did not experience it locally, that was the funny business and why I wondered if it was something on Google side. Or ar there any other build logs you are refering to? – vonGohren Aug 25 '21 at 16:21
  • 1
    That’s the same Cloud Build I was referring to, vonGohren, good probe work. – Anant Swaraj Aug 26 '21 at 11:04
0

It does seem to be a GCP issue and nothing on my side. It started working again now. But it would be great with an issue tracker of somesorts? Or a status page if anyone know about it?

vonGohren
  • 111
  • 3
0

I have experienced the issue. All services were up. I found the solution and I suspect the google cloud platform network (Idk the exact service). Just increase the network timeout. Also increasing the machine type might help.

yarn install --prod --network-timeout 1000000

Artem Dumanov
  • 101
  • 1