Needs destroy-service hook

[stuartpb]

Services with volumes create anything within that volume as root (or at least rethinkdb does). To properly clean up, these services need to be able to run rm -rf from within a container (as root).

[stuartpb]

It's frustrating, because this doesn't mirror init, but it's the right thing to do.

[stuartpb]

The other side of me is saying these services should run as the plushu user instead, but that seems a less tenable solution. (Don't some services manually setuid to their own internal user or something like that?) It's also, strictly speaking, not as flexible for deletion (maybe a service needs to relinquish some hardware resource or something like that? Needs to announce to a cluster that it's going down?)

[stuartpb]

Note that the convention in Dokku was to run the service as the host UID: plushu/plushu-services#2 (comment)

I still don't really think that's tenable, for the reasons laid out in the comment above.

[stuartpb]

TODO: See if there are best practices on this laid out in the Docker docs.