Docker login/logout on all servers for registry operations
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Currently, when a registry is created/updated in Dokploy, docker login runs on either a single user-selected remote server OR the local master node — never both, never all. This means that Docker Swarm worker nodes that weren't selected won't have registry credentials, resulting in image pull failures during deployments.
Describe the solution you'd like
The solution is to automatically enable registry login/logout on all servers (master and all remote workers in the organization) in self-hosted mode.
Describe alternatives you've considered
None
Additional context
No response
Will you send a PR to implement it?
Yes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the registry create and update flows in self-hosted mode, then locate where Docker login and logout are issued for the selected server or master node. Check how the organization’s remote workers are enumerated. Done means registry credentials are applied and removed on the master and every remote worker, with deployments able to pull images from the registry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100