Custom images on Anyscale
Anyscale recommends building a custom image before moving any workload from development to production.
Custom images package environment variables, dependencies, and code assets into an immutable container image. Anyscale provides the following options for building, uploading, and configuring access to custom images:
- Build an image using the Anyscale console, SDK, or CLI. See Build a custom image on Anyscale.
- Reference an image from an external image registry. See Use container images from an external registry.
- Register a custom image in your Anyscale organization. See Register a custom image.
For a tutorial on building custom images and referencing them from an external registry, see Tutorial: Build a custom container image.
You can also edit and use a containerfile to build a custom image during interactive development in an Anyscale workspace. See Iterate on workspace container images.
Anyscale-compatible custom images
Most custom images extend a base image provided by Anyscale. For a full list of base images and their dependencies, see Anyscale base images.
You can build an image that's not based on an Anyscale base image, but must follow minimum specifications. See Requirements for an Anyscale container image.
If you're building your custom image on Anyscale, you can use init scripts to run arbitrary programs as part of the build process. See Use init scripts with custom images.
The Anyscale base images come with a default entrypoint set. Overwriting this entrypoint may break the web terminal and Jupyter notebook server when you launch your cluster.