When you say too demanding, are you referring to downloading dependencies? We recommend running a repository proxy for when that becomes an issue - but there should be nothing in s2i that is more expensive than what docker is already doing. Anything you can share where you don't see that helps us identify possible gaps or recommend fixes.
On Apr 20, 2016, at 7:33 AM, Candide Kemmler <[email protected]> wrote: I have started deploying docker images instead of using the sti pipeline (too demanding resource-wise) I push my docker containers to the docker up. By simply referencing an image with a tag (e.g 'latest') in my deployment config, I am able to deploy my microservices. Now I need to keep them up-to-date. I saw that it is possible to reference a third party registry <https://docs.openshift.com/enterprise/3.0/architecture/infrastructure_components/image_registry.html>. However, doing that I get an "Image pull back off" error. I can't reproduce the message but at some point I think I saw something about "Authentication". Is it btw possible to push directly from my laptop to Origin's internal docker registry? I tried a few things but wasn't successful. _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
