Gravix Layer provides public base templates that are ready to use out of the box. You can also build your own custom templates from public Docker images.Documentation Index
Fetch the complete documentation index at: https://docs.gravixlayer.ai/llms.txt
Use this file to discover all available pages before exploring further.
Public Base Templates
Pre-built templates are available in all supported regions. Built on python:3.14-slim-bookworm.| Template | Resources | Provider / Region |
|---|---|---|
python-3.14-base-small | 1 vCPU / 1 GB RAM / 2 GB disk | azure / eastus2 |
python-3.14-base-medium | 1 vCPU / 2 GB RAM / 4 GB disk | azure / eastus2 |
python-3.14-base-large | 2 vCPU / 4 GB RAM / 8 GB disk | azure / eastus2 |
Build a Custom Template
Custom templates let you define your own environment from any public Docker image. Currently supports Ubuntu, Alpine, and Debian based images.TemplateBuilder Methods
- Base:
from_imageordockerfile - Build steps:
run,apt_install,pip_install,npm_install,copy_file,copy_dir,git_clone,mkdir - Runtime launch:
start_cmd - Readiness:
ready_cmdwithwait_for_portorwait_for_process - Resources:
vcpu,memory,disk - Environment:
env,envs,tags
Manage Templates
Build Status Values
| Status | Description |
|---|---|
queued | Build is queued |
building | Build in progress |
ready | Template is ready to use |
failed | Build failed |
cancelled | Build was cancelled |
Use
build_and_wait for a simple blocking workflow. It starts the build and polls until the template reaches a terminal state.