Publish Your Pod Image to Jina Hub¶
You can contribute your executor into this repository and it will be automatically built into an image and published to the Jina Hub via our CI/CD pipeline.
What Files Need to be Uploaded?¶
Typically, the following files are required:
||describes the dependency setup and expose the entry point;|
||metadata of the image, author, tags, etc. help the Hub to index and classify your image|
||a instruction for guiding users to use your image|
||describes the executor logic written in Python, if applicable;|
||a YAML file describes the executor arguments and configs, if you want users to use your config;|
Note, large binary files (such as pretrained model, auxiliary data) are not recommended to upload to this repository. You can use
RUN wget ... or
RUN curl inside the
Dockerfile to download it from the web during the build.
Your file bundle
awesomeness should be uploaded to:
hub/ | - executors/ | - encoders/ | - awesomeness/ | |- Dockerfile |- manifest.yml |- README.md |- awesome_ai.py
Your image will be published as
manifest.yml must exist if you want to publish your Pod image to Jina Hub.
manifest.yml annotates your image so that it can be managed by Jina Hub. To get better appealing on Jina Hub, you should carefully set
manifest.yml to the correct values.
||Human-readable title of the image (must match with
||Human-readable description of the software packaged in the image||Required|
||contact details of the people or organization responsible for the image (string)||
||URL to find more information on the image (string)||
||URL to get documentation on the image (string)||
||version of the image, it should be Semantic versioning-compatible||
||the name of the distributing entity, organization or individual (string)||
||license under which contained software is distributed, it should be in this list||
||a picture that personalizes and distinguishes your image||None|
||a list of CPU architectures that your image is built on, each item should be in this list||
Please refer to hub/examples/mwu_encoder/manifest.yml for the example.
Steps to Publish Your Image¶
All you need is to publish your bundle into this repo, the Docker image building, uploading and tagging are all handled automatically by our CICD pipeline.
Let’s say your organize all files mentioned in here in a folder called
awesomeness. Depending on what you are contributing, you can put it into
Make a Pull Request and commit your changes into this repository, remember to follow the commit lint style.
Wait until the CICD finish and you get at least one reviewer’s approval.
The CICD pipeline will work on building, uploading and tagging the image on the Jina Hub.
The image will be available at
jinaai/hub.executors.indexers.awesomeness:0.0.0 assuming your version number is defined as
You can use the image as the ways we described here.
Why My Upload Fails on the CICD?¶
Here is the checklist to help you locate the problem.
[ ] Required file
[ ] The required field in
[ ] Some field value is not in the correct format, not passing the sanity check.
[ ] The pod bundle is badly placed.
[ ] The build is success but it fails on three basic usage tests.
Click “Details” and check out the log of the CICD pipeline: