Difficult to getting started with RevPi Connect

I deployed the image to the RevPi Connect from BalenaCloud and it shows up in the dashboard…woohoo!

I’m trying to deploy an application and I can’t get past this:

pull access denied for balenalib/revpi-connect-node, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Looking at this list, there is no image available for the revpi-connect

@floion I see you have worked on the raspberrypi base image adding support for the RevPi Connect with version 2.58.3+rev2. Any suggestions on how to move forward?

Also, until I created an account and started the process, there was no clear way to see which devices are “Community” and which are Official (defined here). Shouldn’t this page include that information, so people can make better decisions purchasing hardware? I also see that “Generic x86_64” is included on the BalenaOS page, but don’t see any reference to it in the Devices dropdown in BalenaCloud or the BaseImage list I linked above. As someone new to this, it’s difficult to learn all these nuances to get started.

Hey @mparris, we are discussing internally the best way to tag device types as community supported only. But in the meantime for your use case, you could use a base image with a compatible architecture instead.

  • If you’re using a Dockerfile.template you can replace %%BALENA_MACHINE_NAME%% with %%BALENA_ARCH%% to get a compatible image.
  • If you’ve hardcoded balenalib/revpi-connect-node in your Dockerfile you should be able to replace it with balenalib/raspberrypi3-connect-node for a similar base image

I hope this helps!

Thanks, doing the following got me going.

replace %%BALENA_MACHINE_NAME%% with %%BALENA_ARCH%% to get a compatible image.

What device-type should the Generic x86_64 devices be? I don’t see it in the Add new Device page on BalenaCloud:



Hey @mparris, unfortunately you cannot currently add a Generic x86-64 device type to an ARM x64 (aarch64/arm64v8) application. At the moment our applications only support one architecture at a time, so when you push code changes only one image type needs to be built.

If you have a Generic x86-64 device you would need to create another application for that device type, and push your code to both apps if required for both architectures.

Thanks. Could you make that more obvious on the “Add new device” prompt?

Maybe list the architecture that was already created for the application, right above the dropdown for the device type, with some text that only devices supporting this architecture are listed (I see this text in the (?) icon, but not obvious for the new user.

I’m new to Balena, so I’m coming at it with fresh eyes, and hoping to provide feedback for other new users.

I see on a fresh application that all devices are available. Thanks!

Hi Matthew,

I wanted to first thank you for all the feedback. I’ve already started efforts on us adding a column to indicate the Maintainer (balena or Community) on our website (both the OS and Supported Hardware pages). I’ll reach back out when it’s completed just to complete the feedback loop with you. :slight_smile:

As for the drop-down menu, I think there is definitely some re-thinking of how it’s displayed that could be beneficial. Could you confirm that I’ve captured your feedback correctly?

  • there is value in including the Maintainer (balena or Community) next to the DT in this drop-down
  • indicate what architecture the application is when choosing a new DT in the drop-down

I’ll take any corrections you add here and then take them to a Product Call for us to discuss the best path forward, then circle back with you about the results.

I think my confusion is that I was able to download a device base image for the RevPi Connect from the BalenaOS page:

And I see reference to the RevPi-Connect on GitHub here, but when I look on Docker Hub, there is no entry for the RevPi-Connect.

Is this because the RevPi-Connect is “community”?

I reviewed all the devices, and there are many inconsistencies, not just for the RevPi-Connect.
Which of the following sources is the correct list for what devices are supported by BalenaOS:

  1. GitHub Device List
  2. Base Image List
  3. Device Type List
  4. BalenaOS Device List
  5. DockerHub Balenalib page

I compared how each of the sources above include devices:

Thank you for taking the time to provide us with the feedback and creating the sheet. It’s odd that RevPi-Connect’s images aren’t published to DockerHub, I am checking internally with the team regarding the same. AFAIK, the list of devices supported by balena is present in the docs are under Single Board Computers in the docs. Please let us know if you find inconsistencies with the same, I do agree it would be better to add more information about these device types. The sheet that you have created might be a good starting point for us to investigate the discrepancies between the multiple sources that you listed. If you can, it would be really helpful if you can provide us with a viewable link to the spreadsheet that you have created. Thanks! Rest assured, we are working on your feedback and will keep you in touch with the updates.

@vipulgupta2048 Thank you for your invitation to become an official member of the balena team; I accept my first assignment to review the Single Board Computers list of supported devices.

The page you referenced is the most restrictive of the six sources I reviewed. Let me know the best way to provide you the spreadsheet.

I look forward to receiving all my entitled employee benefits, including unlimited devices on Balena Cloud.

Ha! You certainly have gone above-and-beyond on this one. We were quite surprised to see your spreadsheet analysis and appreciate your sharing it with us. You can send it to me directly at kenna@balena.io. :slight_smile: