Container images

Create a service from an imageCopy Anchor Link

In a project, choose Create → Docker image. Enter the image and a service name, choose the networking, then Create and deploy.

• Use name:tag or name@sha256:…. Without a tag, latest is used.
• Images come from Docker Hub (docker.io) or GitHub Container Registry (ghcr.io).
• The image must be public. Private registries and registry credentials are not supported yet.

When the service is created, Raseef resolves the tag to the digest of its linux/amd64 image on the server. The service runs that exact image from then on: pushing a new image under the same tag does not change it.

nginx:1.27-alpine  →  docker.io/library/nginx@sha256:…

Change the image laterCopy Anchor Link

In Settings → Source, the image is set by its full digest (name@sha256:…). Raseef accepts digests from docker.io, ghcr.io, quay.io, registry.k8s.io, public.ecr.aws and gcr.io. Save, then deploy.

Networking and the portCopy Anchor Link

A new image service has No port unless you choose one:

• Private port: reachable by other services in the same environment.
• Public web (HTTPS): gets its own HTTPS address. See Public HTTP.

Enter the port the container listens on. Raseef does not set PORT for image services, so the image must listen on the port you enter.