Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I have used it quite a bit. What I hate about it is that it runs on my single machine and the underlying system updates feel a bit dangerous to do. Also at one point it would endlessly crash after adding another worker to a project and there is no way to debug it easily. I moved almost all the projects to DO Kubernetes now. I had written my own dockerfiles anyways since it means faster deploys. The fact that deployment goes through CI is more of a bonus. The Setup is more involved though


Dokku maintainer here:

Docker updates are usually the stressful ones, not Dokku (I try to call out all deprecations/changes in our Migration guides[1]). You can turn on Docker live-restore[1] to make Docker upgrades safer.

I'd imagine the reason you have crashes is due to not having enough system resources (usually memory) to run your workloads. There isn't too much Dokku can do about that, though I would have loved to see a ticket or something on our chat venues to help debug.

Dokku also supports kubernetes[3] if you still want the Dokku experience, and you can deploy images built in CI[4].

Glad to hear you have a setup that works for you though :)

[1] Upgrading Dokku through different versions: https://dokku.com/docs/getting-started/upgrading/#migration-... [2] Docker live-restore: https://docs.docker.com/config/containers/live-restore/ [3] Kubernetes scheduler plugin: https://github.com/dokku/dokku-scheduler-kubernetes [4] Build from a docker image: https://dokku.com/docs/deployment/methods/git/#initializing-...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: