-
Notifications
You must be signed in to change notification settings - Fork 10
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
Problem with mounting volume and buildstep #8
Comments
Are you running the latest version? I merged #7 which is the same fix in persistent storage. There is also a whole new branch https://github.com/dyson/dokku-docker-options/tree/dokku-merge you can try which provides individual settings per phase. If you wanted to give it a test that would be awesome as it's going to be merged into dokku. Let me know how you go. |
Same problem, dokku-merge branch resolved the issue. Strangely enough the issue wasn't resolved though using the latest master (despite #7 clearly being merged). Ah well, soon this will be official and it will all be magic 😉 |
F****CK!!!! Sorry. Oh man, all the persistent (mounted) data directories on my production system have been wiped. Oh man, oh man, this is not good. |
Sorry for the melt-down there, guys! Recovering from our Linode backup now. Haven't used the backup service much before so hopefully everything works. Unfortunately the backup is 20 hours old, so some data will be lost. Nonetheless, this is why you should aways have backups. @dyson I haven't really looked into the details of the issue, but any idea what caused all my mounted directories to be wiped? Some info about our setup We're running about 6 dokku apps with 10+ persistent/mounted directories hooked up to various app instances. Most directories (or directories nested in other directories) are mounted simultaneously on at least two or more dokku apps (docker instances). I'd love to know what happened so I can ensure I don't repeat the mistake. So any pearls of wisdom you can offer would be immensely appreciated. EDIT: Been running the setup for over 6 months without any major* issues. [*] Well, every time we try update buildstep, run apt-get, upgrade dokku, something invariably breaks. But usually it's easy enough to resolve without any permanent damage. |
Hi,
First off, thanks for creating the plugin.
I've been trying to use this with dokku, however, the -v option seems to interfere with the build process from buildpack. I found a similar issue here with your other plugin (that's resolved now) dokku/dokku#906
The error I see when deploying is the same
rm: cannot remove '/app/data': Device or resource busy
. However, it works fine with the persistent storage plugin.Thanks,
Daniel
The text was updated successfully, but these errors were encountered: