i tried to create an offline capable version of a docker-compose file with torizoncore-builder:
torizoncore-builder push --canonicalize --credentials credentials.zip docker-compose.yml
I’m getting the following error:
Error: Registry name specification is not supported yet (at service 'xena').
The docker container at service ‘xena’ is on a private docker registry on azure.
Are there any plans to support private registries e.g. Azure ?
This is a known limitation in TorizonCore Builder. Our team is aware of it and they are working on a solution, but I have no information about when it will be available.
The only “workaround” now would be to use to use a DockerHub registry. Might be useful to at least test the feature and figure out the entire workflow, maybe using a non-sensitive sample instead of your own application.
I reply here to support the same request - this is another showstopper for us currently.
Our company policy does not allow pushing the source codes or binaries outside the company servers.
In June 15th, we have already fixed one of the issues regarding private registry TLS certificate used during bundling:
Looks good and thank you for providing your changes as a reference. This will be a big help to the team when they get around to this task.
I’ll try to remember to inform you once you’ve formally added this feature from our side. For the meantime feel free to use your patched version of TorizonCore Builder for your use case here.
Is there a possibility to increase the priority of the support for the private registries among whole torizoncore-builder?
While we are aware of this limitation. In the meantime there is a work-around detailed on the issue tracker here:
TorizonCore Builder Issue Tracker
Thank you for pointing out this workaround. I found out it in the mean time. I have prepared a modification of TCB to support private registries. I will share it here after clean-up.
In separate topic I will write about an issue when using “platform push” in TCB build from github.