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
[0mThe 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-chrom...
How can I fix this?
Solved! Go to Solution.
Views
Replies
Total Likes
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.
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.
Views
Likes
Replies
Views
Likes
Replies