[{"_1":2,"_172":-5,"_173":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_151":152},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":85,"_104":105,"_142":-5,"_143":11,"_144":17,"_145":11,"_146":-5,"_147":11,"_148":-5,"_149":150},"canonicalUrl","https://hub.docker.com/r/openshiftkatacoda/python-wheelhouse/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","openshiftkatacoda","reponame","python-wheelhouse","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":17,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2017-07-21T02:02:04.171198Z","description","Sample S2I builder for implementing a Python wheelhouse.","is_private","last_updated","2019-04-03T08:28:15.181941Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",9287,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","Python Wheelhouse\n=================\n\nThis repository contains a sample implementation of a [Source-to-Image (S2I)](https://github.com/openshift/source-to-image) builder image for generating Python wheels.\n\nTwo different ways are provided for building the S2I builder image. The first uses a ``Dockerfile`` to build the image from a generic S2I base image. The second uses a Python S2I builder to generate a new custom S2I image which overrides the existing behaviour of the Python S2I builder image.\n\nThe ``s2i`` command line tool mentioned in these instructions can be downloaded from:\n\n* https://github.com/openshift/source-to-image/releases\n\nBuilding the Image from the Dockerfile\n--------------------------------------\n\nTo build the image from the ``Dockerfile``, checkout this source code repository and run ``docker build``.\n\n```\ndocker build -t python-wheelhouse .\n```\n\nIf wishing to build the image in OpenShift, you can use:\n\n```\noc new-build --strategy=docker --name python-wheelhouse \\\n --code https://github.com/openshift-katacoda/python-wheelhouse\n```\n\nNote that when building from the ``Dockerfile``, the resulting image will be for Python 3.5.\n\nBuilding the Image Using Python S2I\n-----------------------------------\n\nTo build the image using the Python S2I builder, checkout this source code repository and run ``s2i build``. You can use the builder for the version of Python you want to use.\n\nFor Python 3.5 you would use:\n\n```\ns2i build . centos/python-35-centos7 python35-wheelhouse\n```\n\nFor Python 2.7 you would use:\n\n```\ns2i build . centos/python-27-centos7 python27-wheelhouse\n```\n\nIf wishing to build the image in OpenShift, for Python 3.5 you would use:\n\n```\noc new-build --strategy=source --name python35-wheelhouse \\\n --code https://github.com/openshift-katacoda/python-wheelhouse \\\n --image-stream python:3.5\n```\n\nFor Python 2.7 you would use:\n\n```\noc new-build --strategy=source --name python27-wheelhouse \\\n --code https://github.com/openshift-katacoda/python-wheelhouse \\\n --image-stream python:2.7\n```\n\nUsing the ``s2i`` Command Line Tool\n-----------------------------------\n\nTo use the S2I builder image created locally with the ``s2i`` command line tool run:\n\n```\ns2i build python35-wheelhouse \n```\n\nReplace ```` with a local file system path, or a URL for a hosted Git repository which contains the ``requirements.txt`` file describing the packages you want to turn into wheels. Replace ```` with the name you wish to use for the container image created.\n\nUse whatever technique is appropriate for your situation to copy the wheels created from the image. The wheels are located in the directory ``/opt/app-root/wheelhouse``.\n\nUsing the Builder Image with OpenShift\n--------------------------------------\n\nIf using OpenShift, to generate Python wheels for the packages required by an application, run:\n\n```\noc new-build --name -wheelhouse \\\n --image-stream python35-wheelhouse \\\n --code \n```\n\nThe source files for the application should include a ``requirements.txt`` file listing the required Python packages.\n\nFor a working example, try:\n\n```\noc new-build --name blog-wheelhouse \\\n --image-stream python35-wheelhouse \\\n --code https://github.com/openshift-katacoda/blog-django-py\n```\n\nThe resulting wheelhouse image is then used as an image source in the build configuration for an application.\n\n```\noc new-build --name \\\n --image-stream python:3.5 \\\n --code \\\n --source-image -wheelhouse \\\n --source-image-path /opt/app-root/wheelhouse/.:.s2i/wheelhouse \\\n --env PIP_FIND_LINKS=.s2i/wheelhouse\n```\n\nThe ``PIP_FIND_LINKS`` could also be set in a ``.s2i/environment`` file, or in a custom ``assemble`` script.\n\nFor a working example which automatically detects the presence of the wheelhouse directory via a custom ``assemble`` script and sets ``PIP_FIND_LINKS``, try:\n\n```\noc new-build --name blog \\\n --image-stream python:3.5 \\\n --code https://github.com/openshift-katacoda/blog-django-py \\\n --source-image blog-wheelhouse \\\n --source-image-path /opt/app-root/wheelhouse/.:.s2i/wheelhouse\n```\n\nWhen the build has finished, then deploy the image:\n\n```\noc new-app --image-stream blog\noc expose svc/blog\n```\n\nWhenever the ``requirements.txt`` file is changed to add more Python packages, trigger a rebuild of the wheelhouse. Subsequent builds of the application will then be quicker as they will reuse the Python wheels from the wheelhouse image.\n\nHow to Run a Disconnected Build\n-------------------------------\n\nThe examples above rely on you still having access to PyPi to download the Python packages when building the wheelhouse. When building the application using the wheelhouse, it acts a local repository to speed up installs. If a version of a package isn't in the wheelhouse, or the version of the package is not pinned and a newer version is available on PyPi, then the package will still be downloaded and installed from PyPi.\n\nTo create a Python wheelhouse and use it for builds in a totally disconnected environment where no Internet access is available, some additional steps and configuration are required.\n\nFor a disconnected build you first need to download all the Python packages you want to be able to later install when the application is being built and deployed in OpenShift. Obviously for this step you will need to have Internet access available.\n\nCreate an empty directory to contain all the packages you want to pull down and populate the Python wheelhouse with. Add to this directory the ``requirements.txt`` file listing the packages. Run the command:\n\n```\npip download -r requirements.txt --dest packages\n```\n\nThis will populate the ``packages`` subdirectory with everything which is downloaded.\n\nBecause the Python S2I builders bundled with OpenShift do not always have the latest versions of the ``pip``, ``setuptools`` and ``wheel`` packages, the wheelhouse when being built will first attempt to update them to the latest version. If this is not done, various Python packages may not install correctly due to bugs in the older versions of these packages.\n\nYou should also therefore run the following command to pull down latest versions of these packages.\n\n```\npip download pip setuptools wheel --dest packages\n```\n\nNote that the above commands only download packages, they do not attempt to compile packages which have C extension components.\n\nNext we create the wheelhouse image from this directory. We are going to use a binary input build so the first create the build configuration.\n\n```\noc new-build --name -wheelhouse --binary \\\n --image-stream python35-wheelhouse \\\n --env PIP_FIND_LINKS=packages \\\n --env PIP_NO_INDEX=true\n```\n\nThe ``PIP_NO_INDEX`` environment variable ensures that ``pip`` does not try and pull down packages from PyPi. The ``PIP_FIND_LINKS`` environment variable tells ``pip`` to instead look in the ``packages`` subdirectory where all the downloaded packages are installed.\n\nTrigger the build, uploading the contents of the current directory as the input for the build.\n\n```\noc start-build -wheelhouse --from-dir=.\n```\n\nThe wheelhouse has now been created which contains all required packages, compiled into Python wheels.\n\nA build configuration for the application is created similar to before, but with the ``PIP_NO_INDEX`` environment variable also being set so ``pip`` doesn't attempt to download packages from PyPi.\n\n```\noc new-build --name \\\n --image-stream python:3.5 \\\n --code \\\n --source-image -wheelhouse \\\n --source-image-path /opt/app-root/wheelhouse/.:.s2i/wheelhouse \\\n --env PIP_FIND_LINKS=.s2i/wheelhouse \\\n --env PIP_NO_INDEX=true\n```\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",10922357371,"orgData",{"_86":87,"_88":89,"_90":91,"_92":29,"_93":94,"_95":94,"_96":94,"_97":94,"_98":99,"_100":94,"_101":94,"_102":94,"_103":17},"id","bfe0748bd9d0425488a36b03e3043bcd","uuid","bfe0748b-d9d0-4254-88a3-6b03e3043bcd","type","organization","orgname","full_name","","location","company","profile_url","date_joined","2017-03-15T09:34:30.087843Z","gravatar_url","gravatar_email","badge","is_active","recentTags",[106],{"_107":40,"_108":109,"_110":111,"_86":112,"_113":114,"_46":131,"_132":109,"_133":29,"_134":52,"_53":135,"_136":137,"_138":122,"_139":131,"_140":62,"_141":17},"content_type","creator",1555772,"full_size",227356277,13175458,"images",[115],{"_116":117,"_118":119,"_120":94,"_121":122,"_123":124,"_125":126,"_127":94,"_128":-5,"_129":111,"_59":62,"_130":-5},"architecture","amd64","digest","sha256:930ac37ee44b1b8ddcc6662ce2e6dffee97186490d4f0c9fb3d04f44afdceeab","features","last_pulled","2026-09-27T09:52:49.296509436Z","last_pushed","2019-04-03T08:28:15Z","os","linux","os_features","os_version","size","variant","2019-04-03T08:28:14.81507Z","last_updater","last_updater_username","media_type","latest","repository",1669795,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":153,"_160":161,"_149":170,"_171":11},{"_36":154,"_38":155,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":156,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":157,"_75":17,"_76":159,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":158},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_162":60,"_163":-5,"_164":-5,"_165":166},"count","next","previous","results",[167],{"_107":40,"_108":109,"_110":111,"_86":112,"_113":168,"_46":131,"_132":109,"_133":29,"_134":52,"_53":135,"_136":137,"_138":122,"_139":131,"_140":62,"_141":17},[169],{"_116":117,"_118":119,"_120":94,"_121":122,"_123":124,"_125":126,"_127":94,"_128":-5,"_129":111,"_59":62,"_130":-5},[],"canDeleteTags","actionData","errors"]

openshiftkatacoda/python-wheelhouse

Tags for openshiftkatacoda/python-wheelhouse