Deploy via Docker Image
In addition to connecting a GitHub repository, you can deploy directly from a pre-built Docker image. This is useful when you already have an external CI/CD pipeline or want to deploy third-party images.
How it works
When you choose the Docker Image option during service creation, you provide the image reference (name and tag). Guara Cloud pulls the image from the registry and starts the service directly, skipping the build step entirely.
Specifying the image
Provide the full image reference, including the tag:
my-user/my-app:latest
my-user/my-app:v1.2.3
ghcr.io/my-org/my-service:mainSupported registries
Guara Cloud supports images from any registry that speaks the OCI Distribution Spec V2:
- Docker Hub (public or private) —
user/image:tag - GitHub Container Registry —
ghcr.io/org/image:tag - Google Container Registry, Quay.io, GitLab, Harbor, … — use the full image URL
- Any V2-compatible registry, public or private
For private images, attach credentials directly to the service. See Private container registries for the full flow.
Configuration
When deploying a Docker image, you need to configure:
- Port — the port your application exposes inside the container
- Environment variables — configurations needed for the application to work
These settings can be changed at any time in the service configuration.
When to use Docker image vs GitHub
| Scenario | Recommendation |
|---|---|
| Source code in a GitHub repository | Deploy via GitHub |
| External CI/CD pipeline that produces images | Docker image |
| Third-party image (e.g., database, proxy) | Docker image |
| Quick prototyping from source code | Deploy via GitHub |
| Pre-optimized and tested image | Docker image |
Updating the image
To deploy a new version of your image, go to the service settings, update the image reference (for example, from v1.2.3 to v1.3.0) and start a new deployment. Guara Cloud will pull the new version and replace the current container.