Hi, I’m building an extension for BlueOS, but I don’t want to publish it publicly. I’ve pulled the repo on to the Raspberry Pi, and I can run my extension’s server from there and use it fine, but when I create the docker image and attempt to create the extension manually from the local image it always just says “Failed to pull extension xxxx.xxxx:latest”, and doesn’t elaborate as to why. Anyone have any insight on this? I’ve tried many different ways, but I haven’t managed to make any progress. To clarify:
- I have built the docker image locally via the red-pill terminal
- I have confirmed that the docker image name and tag match
- I have confirmed that the image is active via “docker images”
Any help would be greatly appreciated!
Hi @misterlister-
Welcome to the forums!
What you’re trying to do isn’t supported - you can only install docker extensions from Docker Hub - at least on BlueOS stable versions!
If you update to BlueOS 1.5 latest beta (37 currently) you gain the option to install extensions via uploaded .tar file. So compile for the appropriate arch, and upload via that option - let us know if you have issues with this approach!
That makes sense, thanks for the confirmation! Is there a way to install them from a private docker hub repo? I tried unsuccessfully, but I may have not done it correctly. I logged into the same docker hub account in red-pill, but it still didn’t work for me.
Hey @misterlister ,
I believe it’s not possible from a private docker hub repository but you can make extensions private by exporting your docker image to a .tar file and uploading it that way as @tony-white said. You will need to be in a 1.5 BlueOS beta for this to work.