GitLab Container Registry push fails with dynamic image name (suffix) → insufficient_scope

To Reproduce

When using Dokploy with GitLab Container Registry, image push fails due to Dokploy generating a dynamic image name with a random suffix that does not match an existing GitLab project path.

Dokploy builds and attempts to push an image like:

registry.gitlab.com//-

However, GitLab Container Registry only allows pushing to existing project paths, such as:

registry.gitlab.com//

As a result, the push fails with:

insufficient_scope: authorization failed

Logs
push access denied, repository does not exist or may require authorization
server message: insufficient_scope: authorization failed

OAuth request example:

scope=repository:/-:pull,push

Current vs. Expected behavior

Current Behavior

Dokploy automatically appends a random suffix to the image name during deployment:

-

The resulting image is pushed to:

registry.gitlab.com//-
GitLab Container Registry only allows pushing to existing project paths

Since this path does not exist as a GitLab project, the push fails with:

insufficient_scope: authorization failed
Expected Behavior
Dokploy should be compatible with GitLab Container Registry by:

Allowing explicit image name override:

registry.gitlab.com//
Making the random suffix optional or configurable
Ensuring the generated image name maps to an existing GitLab project path
With correct configuration:
Image push should succeed
No manual workaround (e.g., creating new projects for each deploy) should be required

Provide environment information

Dokploy version: v0.29.x
Registry: GitLab Container Registry
Registry URL: registry.gitlab.com
Authentication: Personal Access Token (api, read_registry, write_registry)

Which area(s) are affected? (Select all that apply)

Remote server

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

This issue makes GitLab Container Registry integration unreliable without workarounds. The problem is not related to authentication but to repository path mismatch.

Will you send a PR to fix it?

Maybe, need help

Start by tracing where Dokploy generates the deployment image name and where the image is pushed to the configured registry. Reproduce the deployment against GitLab Container Registry, then verify that the configured or generated repository path matches an existing GitLab project and that the push succeeds without creating projects for each deployment.