"Cannot start container" on fresh install

[mhuebert]

I'm on a new DigitalOcean droplet (Ubuntu Dokku v0.3.15 on 14.04). I've followed the instructions for installing dokku and this plugin, and am now trying to deploy a simple node app.

When I run rethinkdb:create foo, and then deploy to foo, I see the following:

-----> Discovering process types
       Procfile declares types -> web
-----> Releasing web...
-----> Deploying web...
-----> Starting linked container rethinkdb_web ...
5cab6a6b6adb50813bcc426d5a274dc0ee25fd0cda3ab997a97aa34efc098370
remote: time="2015-03-04T08:51:00-05:00" level="fatal" msg="Error response from daemon: Cannot start container 5cab6a6b6adb50813bcc426d5a274dc0ee25fd0cda3ab997a97aa34efc098370: exec: \"--bind\": executable file not found in $PATH"

When I first deploy an app to other_foo, and then run dokku rethinkdb:create other_foo, I see:

-----> Creating new RethinkDB volume for other_foo
-----> Releasing other_foo ...
Releasing image source type  not supported!

I'm not sure how to debug this, and I am new to docker. I am able to deploy the same node server to a different app (not created w/ rethinkdb:create) successfully.

[stuartpb]

The first error looks like it's probably a consequence of me changing the image used by this plugin from crosbymichael/rethinkdb to the official one, and not stopping to remember that "rethinkdb" was the ENTRYPOINT for the former, while "rethinkdb --bind all" is the CMD for the latter. The change I just pushed should fix this. No idea about the second one - if the same change doesn't fix it, sounds like a bug in Dokku.

FYI, I don't use this plugin, or even Dokku, any more. I've written a successor, Plusku, that is much more extensible, and it has a much more versatile "addons" system that supports creating a wide range of services (including Redis and MongoDB) with the same level of integrity (surviving restarts etc) as this plugin provides just for RethinkDB.