Repository navigation
Environment variables from the UI are deployed with surrounding double quotes in Docker Swarm Compose stacks #5096
Description
To Reproduce
Create a Docker Compose project in Dokploy.
Configure a variable in the Environment tab:
QUARKUS_LOG_SENTRY_DSN=https://[email protected]/0000000000000000
Reference it in the Compose service:
services:
backend:
environment:
QUARKUS_LOG_SENTRY_DSN: ${QUARKUS_LOG_SENTRY_DSN:?QUARKUS_LOG_SENTRY_DSN is not defined}
Deploy the project as a Docker Swarm stack.
Inspect the failed Swarm task/container configuration.
Observe that the environment variable contains literal surrounding double quotes.
The generated Dokploy .env file also contains the quotes:
first=["] last=["] length=94
The expected unquoted value is:
first=[h] last=[4] length=92
The failed container task receives the same quoted value:
first=["] last=["] length=94
Current vs. Expected behavior
Expected behavior
The service should receive the exact value entered in the Environment tab, without additional quote characters:
QUARKUS_LOG_SENTRY_DSN=https://...
Characters inside the value, such as :, /, @, = and _, should be preserved without requiring users to add quotes manually.
Actual behavior
The deployed Docker Swarm service receives:
QUARKUS_LOG_SENTRY_DSN="https://..."
The quotes become part of the value and cause URL parsing to fail.
Provide environment information
Dokploy version: Version v0.30.0
Deployment type: Docker Compose / Docker Swarm
Compose deployment mode: Stack
Dokploy topology: Dokploy manager with remote production nodes
Application runtime: Quarkus / Java
Number of Swarm nodes: 2Which area(s) are affected? (Select all that apply)
Docker Compose
Are you deploying the applications where Dokploy is installed or on a remote server?
Remote server
Additional context
No response
Will you send a PR to fix it?
Maybe, need help
Activity
linear-code commentedon Aug 16, 2026
DOK-645
dosubot commentedon Aug 16, 2026
Hi @ThiagoCrepequer! I'm Dosu and I'm helping the Dokploy team.
I can pinpoint exactly where this double-quote issue originates in the codebase. The root cause is in how the
.envfile is generated for stack deployments.The
.envfile —prepareEnvironmentVariablesForFileIn
packages/server/src/utils/docker/utils.ts, every value written to the.envfile is explicitly wrapped in double quotes:This is valid dotenv syntax —
docker compose(non-stack mode) correctly strips those quotes when reading the file. However,docker stack deploydoes not strip dotenv quotes during variable substitution, so the literal"characters become part of the value.How the
.envfile gets written for stack deploysThe
getCreateEnvFileCommandfunction callsprepareEnvironmentVariablesForFileand writes the result to disk. So your valuehttps://examplePublicKey@...becomes"https://examplePublicKey@..."in the file. Whendocker stack deploysubstitutes${QUARKUS_LOG_SENTRY_DSN}from this.envfile, the quotes are included as literal characters.Note that for stack deploys, Dokploy also inlines variables into the shell via
env -iusinggetExportEnvCommand, which usesshell-quotefor proper shell escaping. Butdocker stack deployperforms its own variable substitution from the.envfile rather than the shell environment, so the double-quoted.envvalues are what actually get interpolated.Root cause summary:
prepareEnvironmentVariablesForFilewraps all values in"..."for dotenv safety, which works fordocker composebut breaksdocker stack deploybecause the latter treats quotes as literal value content.The fix would need
prepareEnvironmentVariablesForFileto avoid wrapping values in double quotes when the target is a stack deployment (or use an escaping strategy thatdocker stack deployhandles correctly), while still escaping special characters like$and#.This is closely related to #4694, where @Siumauricio confirmed the underlying issue and noted that the fix requires proper quoting/escaping when serializing values into
.env[1].Workaround for now: You can try base64-encoding the value and decoding it at runtime in your application, as other users affected by #4694 have done.
To reply, just mention @dosu.
Docs are dead. Just use Dosu.
test: assert Sentry DSN is emitted without surrounding quotes
JerresonJ commentedon Aug 17, 2026
This is killing us… all our stacks are unmanageable now.
Not only is .env getting quoted, but we’ve noticed stack compose health checks getting mangled too.
Can we get a patch out soon as possible here.
docker stack deploydoes not strip quotes) #5113 as a duplicate of this issuefix: don't quote .env values for stack deploys
chore(release): 0.42.0 [skip ci]