Use a public Docker Hub image as the source for a PD DigitalOcean App Platform service. The module accepts a repository and optional tag; saving it requests a deployment.

Prepare the image reference

Use the Docker Hub form namespace/repository:tag. For images published without a user namespace, use the repository name and tag. This is an image reference, not a registry login, a full registry URL, a Docker Compose file or an image digest. Do not paste registry passwords or tokens into the source field.

Choose an image you can access publicly and a deliberate tag for the intended application release. When no tag is supplied, the module uses latest, which can refer to different content over time. DigitalOcean’s container deployment guide documents its Linux AMD64 image requirement. A reference passing the module’s format check is not proof that the image exists or runs successfully.

The module’s source workflow creates one web-service component. Confirm the image is suitable for that app-hosting workflow; this form does not provide a general container runtime configuration editor.

Submit the image

1. Open the service’s Information tab in the Blesta client area for the intended app service.
2. Find the App source form.
3. Enter the public Docker Hub repository reference with its intended tag. The branch field is for Git sources and does not select a container version.
4. Review the intended service, then choose Deploy when ready. An initial source submission can create a provider app; changing an existing source requests a new deployment.
5. Read the response and follow the service’s state and Activity until the requested deployment has an outcome.

Verify the new deployment

Open the live URL when the deployment is ready and confirm the expected application release. A working previous version does not prove that the new image was deployed. If the image is missing or private, correct its public reference and tag rather than adding credentials to this field.

For a failed build or startup, review the image’s architecture and compatibility with App Platform’s runtime requirements. Do not infer automatic deployment after pushing a new Docker Hub tag; use the module’s intended Redeploy action when you want to request another deployment.

If an action’s outcome is uncertain, check the latest operation before repeating it. Do not send registry credentials, provider tokens or private application data.

See the PD DigitalOcean App Platform Blesta guide for related setup, or explore PD DigitalOcean App Platform.