Yes. I can actually manually pull it from nexus on any openshift node. Because we use an internally signed certificate I was wondering if it might have something to do it with? The node is able to pull because I put the certificates into /etc/pki. Not sure the builder image has that information.
W0808 08:53:09.780779 31667 util_unix.go:75] Using "/var/run/crio/crio.sock" as endpoint is deprecated, please consider using full url format "unix:///var/run/crio/crio.sock".
Image is update to date for nexus.example.com:8500/openshift/nodejs sha256:7b26a9d8ace47e939a9fcdca61620dbe47d1b936e68983e252cca50991704c7c
From: Adam Kaplan [mailto:adam kaplan redhat com]
Have you pushed the nodejs s2i image to your nexus registry? The ansible playbook does not do this for you.
If you haven't done so, you can manually pull the nodejs s2i image from registry.access.redhat.com, then push it to the nexus registry.
On Mon, Aug 13, 2018 at 9:16 AM Sandrini, Christian <Christian Sandrini bis org> wrote: