-
-
Notifications
You must be signed in to change notification settings - Fork 86
Open
Labels
bugSomething isn't workingSomething isn't working
Description
To Reproduce
- Have existing Docker Swarm setup.
- Follow steps under docs/manual_installation
Current vs. Expected behavior
- expected to have a working Dokploy instance running
- Docker service that fails to start.
Provide environment information
Operating System:
OS: Debian 12
Arch: x86_64
Dokploy Version: 0.26.3, 0.25.11Which area(s) are affected? (Select all that apply)
Installation
Additional context
I already have an established Docker Swarm instance with dozens of services and looking to migrate from Portainer. I noticed the install script re-inits the Docker Swarm cluster which would disrupt many services.
I followed the steps under Manual Installation only to get multiple errors:
- NodeJS crash
dokploy.1.ywgfml077pif@test-server | # node[1]: std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start() at ../src/node_platform.cc:68
dokploy.1.ywgfml077pif@test-server | # Assertion failed: (0) == (uv_thread_create(t.get(), start_thread, this))
- Running as a stand-alone docker service with "security-opt seccomp=unconfined", get "Make sure you have installed Redis" errors.
Only after reading install.sh script do I realize I must:
- Update REDIS_HOST to existing docker service instance
- Create Postgresql User/Password/DB and pass in via DATABASE_URL with the only example I can find being in https://github.com/Dokploy/dokploy/blob/068deecb61516b86457c3618744477f003987023/apps/dokploy/.env.production.example#L1
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working