Upgrade plugin for usage with 0.4.x

[josegonzalez]

No description provided.

[caioariede]

👍

[sbehrends]

Is this branch working? I added it as a plugin to Dokku, volumes are generated but they will never mount on docker.

[josegonzalez]

No idea, all I did was a basic upgrade.

[sbehrends]

It's not mounting the volumes on docker. Looks like the env var is not being passed as a config.

[ebeigarts]

There is no docker-argshook anymore, instead there is docker-args-deploy, docker-args-build, docker-args-run

root@dokku:/var/lib/dokku/plugins/enabled/volume# ln -s docker-args docker-args-deploy
root@dokku:/var/lib/dokku/plugins/enabled/volume# ln -s docker-args docker-args-run

[sbehrends]

Good solution ;)
Any clue on how fixing permissions? One container writes files with it's gid and on next boot gid changes and dont have permissions

[ebeigarts]

@sbehrends i'm not having this issue (dokku 0.4.1, docker 1.8.2 aufs)

[sbehrends]

Had to add "-e USER=nobody" so it's always same users that writes that volume.

[josegonzalez]

Updated the docker args stuff for 0.4.x.

[ebeigarts]

docker-args-build got my volumes wiped out, the herokuish build process does some weird cleaning after build process...

[josegonzalez]

Okay, so I'll drop that one.

[josegonzalez]

bump

[EpicVoyage]

I installed dokku-volume and then applied this patch against /var/lib/dokku/plugins/available/volume. Once I realized that docker-ags-deploy needed chmod +x, everything began to work correctly.

This patch has my vote.

[alessio]

👍

[cveilleux]

+1 please merge

[Kikobeats]

I tested that @josegonzalez PR works fine in the last version of dokku, so @ohardy go ahead!

[Kikobeats]

why not merge this?