Are images on Docker hub out of date in respect to OS packages? about s2i-python-container HOT 5 CLOSED

Confirmed that blows up if build is done on OpenShift instance itself. That is, the following fails:

$ oc new-build https://github.com/GrahamDumpleton/openshift-s2i-python-experiments.git --context-dir=httpd-py27-1 --name httpd-python-27-centos7

To fake it out and get it to work I can build openshift/python-27-centos7 locally on OpenShift using:

oc new-build https://github.com/openshift/sti-python.git --context-dir=2.7 --name=xpython-27-centos7

This creates image stream for the S2I Python builder called xpython-27-centos7.

I can then edit the bc for httpd-python-27-centos7 and change to:

                "strategy": {
                    "type": "Docker",
                    "dockerStrategy": {
                        "from": {
                            "kind": "ImageStreamTag",
                            "name": "xpython-27-centos7:latest"
                        }
                    }
                },

That is, pick up the image stream for my local built version of python-27-centos7 and then my build for my derived image works fine.

Thus there is definitely an issue with the Docker image on Docker Hub being out of date in respect of operating system package versions. It will have to be rebuilt to allow any images derived from it to build.

This could be an ongoing issue if changes to operating system packages for systemd are going to make the image periodically unusable as a base image until rebuilt.

The root cause needs to be properly understood.

from s2i-python-container.

openshift/python-27-centos7 is a dead image. The right image is centos/python-27-centos7

i tested your dockerfile w/ that image and things work.

from s2i-python-container.

If openshift/python-27-centos7 (and other openshift/python-* packages) are regarded as dead and shouldn't be used, then there should be a warning in the descriptions on Docker Hub Registry pointing at what images should be used instead.

Better still, the images should be replaced with one which is effectively:

FROM centos/python-27-centos7

ONBUILD RUN echo "WARNING: The 'openshift/python-27-centos7' image is deprecated, use 'centos/python-27-centos7' instead"

and which is still updated each time the base image is updated.

This way users who were using the image under the old name will still get updates, plus get a warning when building a derived image that they are using an image name which is deprecated.

This avoids problems with Docker Hub Registry just becoming a graveyard for obsolete and unmaintained images where people are none the wiser that they are using old images.

from s2i-python-container.

@GrahamDumpleton I like that idea, @bparees ? @hhorak ?

from s2i-python-container.

to be clear, openshift/python-33-centos7 is not dead. We own 33 so it's in the openshift namepsace. SCL owns 27 and 34 so those are in the centos namespace, per their request.

I'm happy to update the dockerhub text, i'm less inclined to update the images themselves as that could break people who are trying to use them as is. I'm less worried about someone new trying to use that image and having it not work, than about breaking someone who still has a reference to it.

And because of the way s2i handles images that have onbuild instructions, adding that is going to make s2i builds extra slow (we will perform a docker build in order to ensure the onbuild instruction gets run).

from s2i-python-container.