marqo-ai/marqo-base

The dependencies and Dockerfile for creating the Marqo base image

marqo-base

The dependencies and Dockerfile for creating the Marqo base image

The marqo-base image is an image that has the necessary dependencies for the Marqo to be installed on and run. This speeds up the build process.

Manage Dependencies

The marqo-base image contains all the dependencies needed to run Marqo. We use pip-compile to to manage the dependencies. It is a part of the pip-tools package and can be installed as

pip install pip-tools

In case you want to add a new dependency, you can add it to the requirements.in file and run

pip-compile requirements.in --output-file=requirements.txt --strip-extras

to generate the requirements.txt file. This file is used to install the dependencies in the Dockerfile. If any of the dependencies/sub-dependencies are not pinned and are updated when you run pip-compile, you should add the new version to the requirements.in file and run the above command again until they converge. We have an automated pipeline for this check. You SHOULD NOT manually update the requirements.txt file for dependencies.

Cross-platform Dependencies:

We use environment markers to manage cross-platform dependencies. For example, we have

torch==1.12.1+cu113; platform_machine == "x86_64"
torch==1.12.1; platform_machine == "arm64" or platform_machine == "aarch64"

The pip-comple tool does not support cross-platform dependencies. If you run pip-compile on the requirements.in file on an x86_64 machine, it will generate the torch==1.12.1+cu113; platform_machine == "x86_64" line, but remove the torch==1.12.1; platform_machine == "arm64" or platform_machine == "aarch64" line, and vice versa.

In such cases, you are supposed to run pip-compile on the requirements.in file on both x86_64 and arm64 machines and generate two requirements.txt files, e.g., amd64-gpu-requirements.txt and arm64-requirements.txt. We do not have seperated files to distinguish between amd64 and amd64-gpu at the moment, but we might have in the future. Here is an example of how to generate the amd64-gpu-requirements.txt file:

pip-compile --output-file=./requirements/amd64-gpu-requirements.txt ./requirements/requirements.in --strip-extras

It is not recommended to merge the cross-platform dependencies into a single requirements.txt file here. Having separate files for different platforms is the best practice.

Build and push a new Marqo-base version to Dockerhub

To release a new version of Marqo-base to Dockerhub:

1. run the push-to-dockerhub workflow with default options. By default, an always-increasing integer will be used as the image tag. The resulting image tag won't necessarily be the previous_tag + 1, as the GitHub run number is used, which also increments on failed runs. If you want to use a different tag, such as "test" you can set it as the second param.

2. You will get a message during one of the steps to review deployments before the image is built and pushed to dockerhub:

Please don't forget about this pipeline when there is a pending review because the ec2 instance used to build the image will still be running until the deployment is approved or the workflow is cancelled. If you are an authorised reviewer, click approve and deploy:

4. The workflow will proceed to push a new version to Dockerhub! If you want to confirm the name of the new marqo-base image that was generated, you can download this artefact.

Pull an ECR image

# 1. Authenticate into the ECR repo
aws ecr get-login-password --region us-east-1 | docker login --username AWS --password-stdin 424082663841.dkr.ecr.us-east-1.amazonaws.com
# 2. Pull your tag
docker pull 424082663841.dkr.ecr.us-east-1.amazonaws.com/marqo-base:my-tag