Using a different docker volume after running dokku couchdb:upgrade <app> ? about dokku-couchdb HOT 4 CLOSED

This plugin doesn't use docker volumes, it writes files to disk directly. You can check the path on disk via dokku couchdb:info $SERVICE. Did you create a backup before upgrading? If so, you can create a new service and import that backup.

from dokku-couchdb.

Thanks @josegonzalez for the fast reply. I do wonder why I was able to find the data in a docker volume in that case... It was in a volume like /var/lib/docker/volumes/829f13aea3499d512fc4f8f71rb77e1dc162148443a1d779047bf475e7f98bbf/_data.

At this point I've copied the contents of that volume back to /var/lib/dokku/services/couchdb/lollipop/data. Still not sure what happened. Again I appreciate your help.

from dokku-couchdb.

Not sure either, but as you see here, we use a directory on disk to back the data volume.

Glad to see you're back up and running (always backup and test your backups!). Feel free to donate to the project if you find it useful, I personally use the money for either cat food or buying myself drinks at a bar, so you know it'll go to a good cause :)

Closing since hopefully there is nothing to do here now.

from dokku-couchdb.

Thanks Jose,

I'm still going through the wreckage to try and piece together what actually happened but I'm totally stumped. You're right that the couchdb dokku plugin doesn't create docker volumes, so I have no idea why there would be a volume containing the data directory. The only thing I can think of is that I created the service using an older version of the couchdb plugin, and maybe that was using volumes?

I tried running the same upgrade sequence on a backup server created from a snapshot, and everything went as expected. If I come up with anything else, I'll post an update here.

And I will definitely be sponsoring the project now. I definitely appreciate the work you're doing. Cats need to eat too!

from dokku-couchdb.