-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: open /var/lib/dokku/plugins/available/shoreman/plugin.toml: no such file or directory #22
Comments
I created a plugin.toml and rebuild my app still not work.
Now I am using logging-supervisord instead. |
Looks like dokku-shoreman isn't compatible with 0.4.x at the moment. Thanks for filing the issue. |
😃 |
Same issue here on 0.4.x. Would love to get this working! |
+1 Same issue here too, can't run more than 1 worker without this plugin. Tried supervisord but runs only 1 worker. |
Same issue here. |
Noob question: how do I remove shoreman from dokku in this scenario? "dokku plugin uninstall shoreman" is not working... Thanks :-) |
Most likely |
Thanks. Ran rm -r /var/lib/dokku/plugins/available/shoreman and now 'dokku plugin' shows a nice clean list again. However, when I want to deploy I get this warning: remote: 2015/11/23 17:08:24 open /var/lib/dokku/plugins/available/shoreman/plugin.toml: no such file or directory and the deploy fails with this message: remote: Error response from daemon: Cannot kill container a1ef2537264fe871d97faa8741b77e4fbfe97fc12a76f727910f665c3d1dbb40: notrunning: Container a1ef2537264fe871d97faa8741b77e4fbfe97fc12a76f727910f665c3d1dbb40 is not running
remote: Error: failed to kill containers: [a1ef2537264fe871d97faa8741b77e4fbfe97fc12a76f727910f665c3d1dbb40] Ideas? :-) Thanks for your time! |
Hi @Corstiaan84 have you checked if there is a symlink on Thanks |
Hi @pmvieira :-). Noob alert! How do I check that and why is it important? I would like to learn more about this. |
@Corstiaan84 do an There are two directories inside /var/lib/dokku/plugins/ : available and enabled. "available" contains every plugin that was installed and not yet uninstalled; So, if you manually uninstalled shoreman, chances are that there is a symlink (AKA a shortcut) pointing somewhere else, and dokku is looking for it but finding nothing. Have a look and if there is a shoreman symlink there, delete it. |
Thanks. Worked :-). |
@pmvieira I've noticed that you've done a fork of the branch...works with dokku 0.4.x ? I've tried but seems not load correctly the workers... |
@riccardoa i just had a quick shot at it, but found the same issue and didn't have time to work on it. |
+1 |
@pmvieira Honestly I've then tried to run the worker like it's explain here: http://progrium.viewdocs.io/dokku/process-management/ and it works perfectly! so it's a bit useless use something like shoreman! (at least in my case where I've only web and worker) |
@riccardoa Could you provide some insights into the steps/config/code you used to get it working? Perhaps create a gist? |
@riccardoa I agree with you, if that's your scenario then what you mentioned is the best approach IMHO and me/we are using it in some projects. Anyway, I just submited a PR since I believe I was able to fix it for Dokku V4 CC: @statianzo |
👍 |
Get an error when I update dokku to 0.4.1.
For 0.4.*, I installed shoreman by
Seems plugin.toml is a meta file, and now I can not start job worker by shoreman.
Any ideas ?
The text was updated successfully, but these errors were encountered: