AEM Cloud pipeline Build image error for downloading chrome binaries | Community
Skip to main content
abhinarvekar
Level 2
February 14, 2025
Solved

AEM Cloud pipeline Build image error for downloading chrome binaries

  • February 14, 2025
  • 1 reply
  • 584 views

The build image stage fails with error

```
W: GPG error: https://dl.google.com/linux/chrome/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 32EE5355A6BC6E42
E: The repository 'https://dl.google.com/linux/chrome/deb stable InRelease' is not signed.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/microsoft-edge-stable.list:1 and /etc/apt/sources.list.d/microsoft-edge.list:3
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/microsoft-edge-stable.list:1 and /etc/apt/sources.list.d/microsoft-edge.list:3
The command '/bin/sh -c apt -qqy update && apt -qqy --no-install-recommends install python curl build-essential' returned a non-zero code: 100
2025/02/13 16:45:20 Container failed during run: build. No retries remaining.
failed to run step ID: build: exit status 100
```
I see there is some discussion on google forum about key being updated https://support.google.com/chromebook/thread/257688390/the-repository-http-dl-google-com-linux-chrome-deb-stable-inrelease-is-not-signed?hl=en 

How can I fix this?

 

Best answer by chaudharynick

Hi @abhinarvekar 

 

Please try retriggering it after some time as can sometimes be network or connectivity issues.

Also, did you recently make any changes in pom.xml, or add any dependency or something that might have caused the issue? If yes, please try reverting that change and see if that is the root cause.

 

If the issue persists, please raise a ticket with Adobe.

1 reply

chaudharynick
chaudharynickAccepted solution
Level 4
February 14, 2025

Hi @abhinarvekar 

 

Please try retriggering it after some time as can sometimes be network or connectivity issues.

Also, did you recently make any changes in pom.xml, or add any dependency or something that might have caused the issue? If yes, please try reverting that change and see if that is the root cause.

 

If the issue persists, please raise a ticket with Adobe.