Build fails on kiosk
Closed this issue · 8 comments
I’m using the blue button to update my release but it fails on kiosk with the following error.
I think this is actually an issue with Balena container registry.
Because v2.9.0 is correct as per... https://hub.balena.io/blocks/1916869/browser-aarch64
Will create a thread on balena forum
https://forums.balena.io/t/balena-container-registry-not-working-for-browser-aarch64/371363
Also I just noticed we had a build with 2.7.0 successful about a week ago and then a day later the build, still with 2.7.0 failed. Must be some issue with bh.cr. As 2.7.0 is failing currently too.
Ok I've discovered something really weird.
If we have in the dockerfile:
ARG BROWSER_VERSION=2.9.0
FROM bh.cr/balenalabs/browser-%%BALENA_ARCH%%/$BROWSER_VERSION AS base
The build fails with the error message:
Error: pull access denied for bh.cr/balenalabs/browser-aarch64/2.9.0, repository does not exist or may require 'docker login': denied : requested access to the resource is denied
But if we instead use:
FROM bh.cr/balenalabs/browser-%%BALENA_ARCH%%/2.9.0 AS base
It builds successfully.
So it appears to not be liking the ARG variable in the FROM line.... Even though it clearly correctly parses it as the error output shows the correct URL for the package bh.cr/balenalabs/browser-aarch64/2.9.0
This seems to be an issue with Balena builders not properly parsing the Dockerfile so even though the error message is parsing the ARG, the builder that's trying to pull the image clearly isn't.
From builder logs:
Step 1/6 : ARG BROWSER_VERSION=2.9.0
Step 2/6: FROM bh.cr/balenalabs/browser-aarch64/${BROWSER_VERSION} AS base
pull access denied for http://bh.cr/balenalabs/browser-aarch64/2.9.0, repository does not exist or may require docker login : denied: requested access to the resource is denied
As a workaround, technically, renovatebot config could be updated to parse out the version from the FROM, then we could drop the ARG again
As a workaround, technically, renovatebot config could be updated to parse out the version from the
FROM, then we could drop theARGagain
Yeah I think that's probably the best way, at least until balena fix the parsing (if at all)
ARGS in the image name should be supported for public bh.cr images now. Can you give it another try?
Yep will check now
ARGS in the image name should be supported for public
bh.crimages now. Can you give it another try?
@klutchell yes it's working now. The latest push succeeded https://github.com/ketilmo/balena-ads-b/actions/runs/10911742222
@serviceman77 you should be good to go now