Pushing production image to private gitlab registry

Dear Toradex team,

Is there a way to push my production docker image to my private gitlab registry rather than to GitHub or to Torizon Cloud, while using the docker-compose file on Torizon Cloud ?

I found the following link that covers GitHub and Torizon Cloud scenario, but nothing for private registry :
Build and Push Applications | Toradex Developer Center.

I am using Torizon IDE 2.

You would save me a lot of time if you could provide me with a procedure.

Best regards,
Fabian

Greetings @fdortu,

I checked with our IDE team about this and it would seem it’s not possible to push to non-Dockerhub registries from our IDE for now. I submitted a feature request for this and the team will take a look and see what they can do.

But for now you’ll just need to manually push your container image to your registry for the time-being.

Best Regards,
Jeremias

Hi Jeremias,

I managed to push my image to my local repo, but I was not able to use it from Torizon Cloud (using the correct path in docker-compose). I had a docker image manifest issue. Sorry for not providing more debug info but, by lack of time, I decided to stop investigating this for the moment and I am using docker hub successfully.

I am still interested in using my local gitlab registry so if your IDE team could provide some info or a special functionality in the future that will be great.

Overal, Torizon IDE 2 is really great :slight_smile:

Best regards,
Fabian

Overal, Torizon IDE 2 is really great

We’re are glad to hear that!.

I am still interested in using my local gitlab registry so if your IDE team could provide some info or a special functionality in the future that will be great.

As I said before I brought this up as a feature request to our team to look at. Is this something you urgently need or is a huge blocker?

From what I understand at the moment the only registry our IDE extension supports is Dockerhub. So it would take some work to support other registries. Especially private registries that would need authentication and such.

Best Regards,
Jeremias

@fdortu, Just to inform you, this functionality is now available in the early-access version of our extension. It will be officially released with the soon-to-be-released version 2.4.0 of our extension.

Now when you run tasks like create-production-image or tcb-platfrom-publish an additional input field will be asked. This “container registry” field is where you can specify which registry to use.

Best Regards,
Jeremias

1 Like