Pipeline docker build fails but works locally

[Alex White]

I have a docker image I want to build through pipelines. I ran some builds locally to remove any bugs and it all builds fine, but on the pipeline, it constantly throws an error trying to find the http://dl.google.com/linux/chrome/deb stable release file.

The docker file:

FROM node:12

ENV NODE_PATH=/usr/local/lib/node_modules

RUN apt-get update 

RUN npm i npm@latest -g 

RUN wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | apt-key add - 

RUN sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' 

RUN apt-get update && apt-get install -y google-chrome-unstable

RUN npm install -g puppeteer karma karma-jasmine karma-chrome-launcher karma-coverage karma-ng-html2js-preprocessor karma-requirejs karma-cli

The pipeline error:

E: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages 404 Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.

Any ideas why this doesn't run in the pipeline but does locally?

[Mark C]

Hi @Alex White

Thank you for reaching out to the community.

We've seen similar reports as well while downloading packages from dl.google.com on Pipelines.
However, as per our team's findings, it appears to be related to the 3rd party resource DNS dl.google.com.
And while they're investigating it suddenly resolved itself without changing anything on our end.

Would it be possible for you to confirm if you're still experiencing the issue as of today?

Regards,
Mark C