Hi,
I am currently developing a python software using the Torizon IDE inside VSCode.
I am pushing my containers inside a docker hub repository using differents Tags which are really usefull when i have to do some tests “on the fields”.
I am using the VSCode task : create-production-image
With this method the container generated doesn’t have the Dockerfile.debug inside.
I really like the approach with the Dockerfile & the Dockerfile.debug and I’m thinking about making a dockerhub container with this approach to be able to accelerate the debuging phase “on the field”.
I still need the version without the debugging (generated by the docker-compose.prod.yml) but i was wondering if it’s possible within the same Torizon IDE / VSCode project to publish inside another docker hub repository ?
My idea is to have one repo with the “stable release” so no need to have the debug terminal and another one which would be the “testing release” which include this time the debug terminal.
I already tried to change the field image inside my docker-compose.yml
version: "3.9"
services:
my-container-debug:
build:
context: .
dockerfile: Dockerfile.debug
image: ${LOCAL_REGISTRY}:5002/my-container-debug:${TAG}
ports:
- 6502:6502
- 6512:6512
- 4840:4840
fbdevice-kilobaser-container:
build:
context: .
dockerfile: Dockerfile
image: ${DOCKER_LOGIN}/my-container:${TAG} #here i tried to change the "path"
ports:
- 6502:6502
- 6512:6512
- 4840:4840
I assume that it’s the file :
createDockerComposeProduction.ps1
which handle the creation of the docker-compose.prod.yml
Do you have any documentation on how to modify it to include the dockerfile.debug inside the docker-compose.prod.yml?
It would be really nice for me to be able to choose between generating the regular docker-compose.prod.yml and maybe the “docker-compose.debug.yml”.
As we use the file settings.json to give the Tag version, maybe we could use in a similar way a variable inside this file to choose with or without debuging?
I have also a question about Torizon.io OTA :
Currently i have 5 Toradex SoM using my container, we are still in a early dev & research phase so I’m still using the command
docker pull mycontainername:tag
to update my SoMs, as I only have 5 boards, It’s still okay to use this method to update my “fleet”.
Still I think that the idea with Torizon.io OTA is really intersting for the future of the project and I’m currently testing it.
I’m not sure to understand really well how it works.
When I give to Torizon.io a new docker-compose.prod.yml (or maybe docker-compose.debug.yml)
Does Torizon.io connect to my dockerhub and search for the container with the same tag as inside my docker-compose file ?
And then accomplish a fleet “docker pull” to update all the SoMs inside the fleet ?
For me it sound kind of crazy to be able to do this whole process with only the docker-compose file.
For me to be able to update my whole fleet with either my docker-compose.prod.yml or docker-compose.debug.yml in one click would be so great !
To be able to switch between a release container or a testing container for my whole fleet in no time would be a truly good thing.
I hope I’ve been clear enough about my intentions regarding these two container versions and my desire to be able to deploy them on all my modules fairly quickly.
Thank you a lot !
