Docs
DataCrunch HomeSDKAPILogin / Signup
  • Welcome to DataCrunch
    • Overview
    • Locations and Sustainability
    • Support
  • GPU Instances
    • Set up a GPU instance
    • Securing Your Instance
    • Shutdown, Hibernate, and Delete
    • Adding a New User
    • Block Volumes
    • Shared Filesystems (SFS)
    • Managing SSH Keys
    • Connecting to Your DataCrunch.io Server
    • Connecting to Jupyter notebook with VS Code
    • Team Projects
    • Pricing and Billing
  • Clusters
    • Instant Clusters
      • Deploying a GPU cluster
      • Slurm
      • Spack
      • Good to know
    • Customized GPU clusters
  • Containers
    • Overview
    • Container Registries
    • Scaling and health-checks
    • Batching and Streaming
    • Async Inference
    • Tutorials
      • Quick: Deploy with vLLM
      • In-Depth: Deploy with TGI
      • In-Depth: Deploy with SGLang
      • In-Depth: Deploy with vLLM
      • In-Depth: Deploy with Replicate Cog
      • In-Depth: Asynchronous Inference Requests with Whisper
  • Inference
    • Overview
    • Authorization
    • Audio Models
      • Whisper X
  • Pricing and Billing
  • Resources
    • Resources Overview
    • DataCrunch API
  • Python SDK
  • Get Free Compute Credits
Powered by GitBook
On this page

Was this helpful?

  1. Containers

Container Registries

DataCrunch Containers service supports any container registry that allows authentication using the standard Docker config.json format. In addition to that, we support the custom authentication methods for Docker Hub, GitHub Container Registry, and GCP Artifacts.

Docker Hub

Use your Docker Hub username and access token (dckr_pat_xxxxx)

GitHub Container Registry

Use your GitHub access token (ghp_xxxx)

GCP Artifacts

Use your GCP service account key file (json format)

AWS ECR

Use your AWS credentials (access_key_id and secret_access_key). It's recommended to create a new IAM user and a keypair for it.

Ensure you assign the ecr:GetAuthorizationToken permission to the IAM role, or our platform will not be able to refresh the token, and container pulls will fail after 12 hours when the token expires.

Custom Registries

Other registries can be authenticated using the keys in config.json.

Here is a sample key in this format:

{
  "auths": {
    "my-private-registry.com": {
      "auth": "bXlwYXNzd29yZA=="
    }
  }
}

Last updated 3 months ago

Was this helpful?