Deploy From Image

Use this flow when you already have a built container image and want Hubfly Space to run it directly.

For the deeper operational guide covering image references, private registries, saved pull credentials, entrypoint and command overrides, image deploy hooks, and CI/CD rollout patterns, use Docker Image Reference.

Supported Flow

  1. Open your project.
  2. Go to New Container.
  3. Choose Docker Image.
  4. Enter the image reference.
  5. For private registries, enter credentials. Only secure registries are supported.
  6. Optionally override entrypoint and command.
  7. Choose resources, storage, runtime, and env vars.
  8. Deploy.

Image reference

Enter the Docker image reference you want to deploy.

For public images without a registry, Hubfly pulls from Docker Hub by default.

Examples:

nginx:latest
postgres:16
redis:7

To pull from a specific registry, include the registry in the image reference.

ghcr.io/owner/image:tag
registry.example.com/project/image:tag

Advanced Overrides

The image flow supports:

  • Entrypoint override
  • Command override

These fields are entered as one argument per line and are passed as arrays.

When To Use This

This is the right option if:

  • Your CI pipeline already builds images
  • You publish images to a registry
  • You want full control over the build outside Hubfly Builder.
  • You want to deploy infrastructure images such as redis, postgres, or nginx
  • Use Deploy From Git if Hubfly Space should build from source.
  • Use Templates if you want prefilled images, ports, env vars, and volumes
  • Use Docker Image Reference for private registry, deploy hook, and production workflow details
Feedback

Was this page helpful?

Tell us whether this page helped you complete the task you came here for.