Skip to content

Comments

feat: allow selecting stored registries for Docker image pull#3678

Open
AceRRR10 wants to merge 2 commits intoDokploy:canaryfrom
AceRRR10:feat/docker-stored-registry
Open

feat: allow selecting stored registries for Docker image pull#3678
AceRRR10 wants to merge 2 commits intoDokploy:canaryfrom
AceRRR10:feat/docker-stored-registry

Conversation

@AceRRR10
Copy link

What is this PR about?

When using the "Docker" source type for an application, users currently must manually enter username, password, and registryUrl for every application. However, Dokploy already has a registry management system (Settings > Registry) where users store registry credentials. This PR adds a dropdown to select a stored registry when configuring a Docker image pull, avoiding redundant credential entry.

Changes:

  • Added a registry dropdown to the Docker provider form. When a stored registry is selected, the manual credential fields (username, password, registry URL) are hidden.
  • Backend saves registryId on the application and clears inline credentials when a registry is selected (and vice versa).
  • buildRemoteDocker and getAuthConfig now use the linked registry's credentials when available, falling back to inline credentials for backward compatibility.
  • Registry URL and username are automatically prepended to the image name (lowercased) for docker pull/tag commands.

Checklist

Before submitting this PR, please make sure that:

  • You created a dedicated branch based on the canary branch.
  • You have read the suggestions in the CONTRIBUTING.md file https://github.com/Dokploy/dokploy/blob/canary/CONTRIBUTING.md#pull-request
  • You have tested this PR in your local instance. If you have not tested it yet, please do so before submitting. This helps avoid wasting maintainers' time reviewing code that has not been verified by you.

Issues related (if applicable)

N/A

Screenshots (if applicable)

image image

Add a registry dropdown to the Docker provider form, allowing users to
select a previously saved registry instead of manually entering
credentials. When a stored registry is selected, its credentials are
used for docker login and the registry URL/username are prepended to
the image name for pulling. Inline credential fields are hidden when
a registry is selected, preserving backward compatibility.
Reverts the automatic prefixing of registry URL/username to the docker
image name, aligning with the existing behavior where users provide the
full image reference (e.g. ghcr.io/user/image:latest) in the Docker
Image field. The stored registry is still used for docker login
credentials only, consistent with how inline credentials worked before.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant