Hi @alvaro.tx,
We run the “create-production-image” task to build a release container image, but we want to use a local registry without pushing it to DockerHub.
If possible, I would like to know how to do this, ideally with TorizonCore Builder. Is there any documentation?
I’m a little confused here you say “create-production-image” which is a task from our VSCode extension. But then you say “with TorizonCore Builder”. Could you be more specific on what it is you want to do exactly?
When you run create-production-image there is a prompt to input your desired docker image registry to store the production container image. Have you tried just specifying your desired local registry in this prompt?
For TorizonCore Builder, again what do you mean? What action do you want to do with a local registry? The bundle command? If yes then again it’s just a matter of specifying the local registry explicitly. There are multiple threads about using TorizonCore Builder bundle command with local registries:
- Try to make a customized TorizonCore with Pre-provisioned Docker-Images - #12 by jeremias.tx
- Pre-provisioned image from local docker - #6 by jeremias.tx
When I run “create-production-image”, docker-compose.prod.yml is created, but the contents from docker-compose.yml do not change.
When I changed “$composeServices = $composeLoad.Services” in L191 of createDockerComposeProduction.ps1 to “$composeServices = $composeLoad.services”, the intended yml was generated. This fixed the issue, but kindly confirm.
I’m confused isn’t this what is expected? You’re running the task to create-production-image therefore a docker-compose.prod.yml file is generated. Why would you expect the non-production docker-compose.yml file to be affected by this?
The expected behavior of the create-production-image task is detailed in our documentation here: Build, Test and Push Applications for Production | Toradex Developer Center
To what extent does the VSCode Extension “TorizonCore Builder” support TorizonCore Builder functions? Is there any documentation with more details?
The primary functionality of TorizonCore Builder support is whatever is supported by the build command yaml specification: TorizonCore Builder Tool “build” command | Toradex Developer Center
Anything else it would be better to just use TorizonCore Builder on the command-line instead of through the extension.
Best Regards,
Jeremias