BETTER_AUTH_SECRET migration script targets wrong container
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
To Reproduce
The script identifies the Dokploy container using DOKPLOY_CONTAINER=$(docker ps --filter "name=dokploy" --format "{{.ID}}" | head -n1) which is too broad. The result is that script execution fails in sh -c "cd /app && pnpm run migrate-auth-secret" because the container it selected does not have /app.
What works is e.g.
DOKPLOY_CONTAINER=$(docker ps \
--filter "label=com.docker.swarm.service.name=dokploy" \
--format "{{.ID}}" \
| head -n1)
Also, https://github.com/Dokploy/dokploy/pull/4834 is still open.
Current vs. Expected behavior
Script should run successfully, but fails to cd into /app.
Provide environment information
Ubuntu 26.04 x86
Dokploy 0.30.5
Which area(s) are affected? (Select all that apply)
Installation
Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
Additional context
No response
Will you send a PR to fix it?
No
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
Search the repository for DOKPLOY_CONTAINER or migrate-auth-secret to find the migration script, then compare its container selection with pull request #4834. Verify the script selects the Dokploy service container and completes cd /app && pnpm run migrate-auth-secret successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100