Environments¶

Environments are the runtime images that a deployment is based on. They are Docker images with the base system, dependencies and libraries required to run your application.

Environment images in UbiOps are identified by their environment name and tag. Environments can have one or multiple tags, and these tags can be used when creating deployments. Each tag can be used by as many deployments as you like.

Examples of environments are an image with vLLM to host an LLM, or a UbiOps request format deployment with a certain Ubuntu and Python version.

Providing your own environment¶

UbiOps comes with a number of environments included. You can also provide your own environment with an existing Docker image or by building it through UbiOps.

• For pushing an image that you have built or saved locally, see Push your Docker environments to UbiOps.
• For building an image with UbiOps, see Building an environment with UbiOps. Note that building an environment in UbiOps is deprecated.

Types of environments¶

Two types of environment images are supported in UbiOps:

• Standalone Docker images that contain an application. For example, images to host LLMs with vLLM, dashboards and more. The environments for these types of deployments often expose an HTTP server and can be integrated with services.
• Legacy request supporting environments. These images are built on top of UbiOps deployment images and contain functionality to integrate with the UbiOps request system.

Most applications use the first type of environment image.

Managing environments¶

You can manage your environments using the WebApp, the Python Client Library and Command Line Interface (CLI).

In the WebApp you can find both the environments that UbiOps offers and your own custom environments through the Environments tab.