I’m able to use torizoncore-builder from command line (bundle to create a local directory containing the bundled images + build) to rebuild TorizonCore with Evaluation Containers starting from TorizonCore.
For this reason my docker-compose.yml has
easy-installer:
bundle:
dir:
I’ve started investigating TorizonCore Builder VS Code Integration as described here, to get the same result as from the command line.
I don’t uderstand how can I launch the bundle command to create the local directory containing the bundled images.
Currently the VSCode integration does not have an option to run the bundle command stand-alone far as I can tell. If you want to do this you’d need to create the local bundle directory separately outside of VSCode using TorizonCore Builder from the command line. Then you can pass this directory into your VSCode project once created.
Otherwise instead of passing a bundle directory you could instead pass your compose file directly in the yaml, as this wouldn’t require running bundle before hand.
Currently the VSCode integration does not have an option to run the bundle command stand-alone far as I can tell. If you want to do this you’d need to create the local bundle directory separately outside of VSCode using TorizonCore Builder from the command line.
Ok. Clear.
Then you can pass this directory into your VSCode project once created.
Do you mean, adding manually the folder to the VS Code project as in the following image?
Otherwise instead of passing a bundle directory you could instead pass your compose file directly in the yaml, as this wouldn’t require running bundle before hand.
Do you mean, using a different tcbuild.yaml with
bundle:
compose-file: ....
instead of
bundle:
dir: bundled_containers
?
I started with compose-file but then I switched to “bundled containers” because otherwise the containers are downloaded every time.
But it’s clear it’s an alternative option.
Do you mean, adding manually the folder to the VS Code project as in the following image?
Well, yes generally just put the bundle directory into a location that is accessible and can be referenced from the tcbuild.yaml. I don’t think it need to be specifically in the VSCode project itself but it helps for organization of course.
Do you mean, using a different tcbuild.yaml with
Yes that is the alternative, though like you said this has the annoying side effect of causing the containers to be downloaded each and every time. Though this can be useful if the container images have changed and need to be re-downloaded anyways.
