You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After reading the docs about base images naming scheme and exploring the base images repository, I don't understand how users can find which versions are usable. From my point of view, I feel lost...
The text was updated successfully, but these errors were encountered:
cailloumajor
changed the title
manifest for balenalib/raspberrypi4-64-debian-node:14.16.1-buster-build not found in local modemanifest for balenalib/raspberrypi4-64-debian-node:14.16.1-buster-build not found in local mode
May 6, 2021
Just tried after disabling local mode, same problem:
If I set the image tag to 14, I get an image with Node.js v14.7.0, quite out-of-date !
cailloumajor
changed the title
manifest for balenalib/raspberrypi4-64-debian-node:14.16.1-buster-build not found in local modemanifest for balenalib/raspberrypi4-64-debian-node:14.16.1-buster-build not foundMay 8, 2021
I just came across the same issue. There appears to be some gaps in the available images for node (perhaps others too, but haven't explored others). The effect of course is that I can't use %%BALENA_MACHINE_NAME%% in my Dockerfiles as the file is only available for some architectures.
Despite the existence of:
After reading the docs about base images naming scheme and exploring the base images repository, I don't understand how users can find which versions are usable. From my point of view, I feel lost...
The text was updated successfully, but these errors were encountered: