RunPod Pod Configuration: Domain Mapping, Persistence, and Docker
Hey RunPod team 
We’re currently running a FastAPI-based service on RunPod and wanted to clarify a few things:
1. Custom domain: Is there a supported way to map our own domain name to a running pod instead of using the default URL?
2. Persistent environment/data: What’s the best practice for persisting both our environment (e.g., Python venv or Conda) and data on a GPU pod so we don’t lose them after restarting or updating the pod? We’re already using /workspace for volumes — is that the recommended approach for this use case?
3. Running Docker inside a pod: Can we run Docker or Docker Compose inside a GPU pod for containerized workflows or is that restricted? If not supported directly, is there a recommended workaround?
We’re currently running a FastAPI-based service on RunPod and wanted to clarify a few things:
1. Custom domain: Is there a supported way to map our own domain name to a running pod instead of using the default URL?
2. Persistent environment/data: What’s the best practice for persisting both our environment (e.g., Python venv or Conda) and data on a GPU pod so we don’t lose them after restarting or updating the pod? We’re already using /workspace for volumes — is that the recommended approach for this use case?
3. Running Docker inside a pod: Can we run Docker or Docker Compose inside a GPU pod for containerized workflows or is that restricted? If not supported directly, is there a recommended workaround?
