Dokploy / Dokploy/dokploy

Support for external docker secrets

Open
#2,417 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

When deploying a Raw Docker compose, Dokploy doesn't let me use an external docker secret.

This is the error I get when deploying.

Container postgresql  Creating
Container postgresql  unsupported external secret postgres_default_password
unsupported external secret postgres_default_password

I do have a secret with that name added to my docker.

$ docker secret inspect postgres_default_password
[
    {
        "ID": "ts9wesgdoan1kbqn3ywtk34he",
        "Version": {
            "Index": 62
        },
        "CreatedAt": "2025-08-19T19:43:00.736362141Z",
        "UpdatedAt": "2025-08-19T19:43:00.736362141Z",
        "Spec": {
            "Name": "postgres_default_password",
            "Labels": {}
        }
    }
]

So I believe I should be able to use this directly with Dokploy Compose.

This might be a previously raise issue, if this is duplicate and someone can find the original one, please tag that one.

Describe the solution you'd like

Ability to deploy docker compose with something like this

secrets:
  postgres_default_password:
    external: true

If there is some other configuration that may have missed, please let me know.

Describe alternatives you've considered

Using file secrets instead of external secrets works, but I want to use the in-built docker secrets as they offer more functionality and organization with labels.

Maybe in the future secrets can be managed from the Dashboard.

Additional context

Dokploy Version: v0.24.12
Docker version 28.3.3, build 980b856
OS : Ubuntu 22.04.5 LTS (GNU/Linux 6.8.0-1030-oracle aarch64)

Will you send a PR to implement it?

Maybe, need help

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Raw Docker Compose deployment path and the handling of Compose secrets. Reproduce the issue with the shown external secret declaration and an existing Docker secret named postgres_default_password. Done means Dokploy deploys the Compose application without reporting an unsupported external secret.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose
Domain
devops, infrastructure
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.