-
Notifications
You must be signed in to change notification settings - Fork 3
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
Persisting storage issue #15
Comments
The files at that path in the container my need to be copied on the first build, before mounting the local path which is probably empty. The unknown host error may be from some default setting. I’m out of the county this week but can help debug when I get back. |
Also, when I run the
I'm assuming they're related |
Aaaand as I just tried, looks like what I had to do was write to a different directory on the container because it was not empty (or I could have removed it). |
I lied, still an issue... can't get this thing to mount |
After many stressful hours, I think I've found the problem... and it was very simple... The volume is being referenced via a relative path that lives within the root directory. If I change it to somewhere else on the system it works... could that be accurate? |
I’m not sure. Are you saying that the host path ./backup_data/postgres caused the issue? Seems odd. |
Yeah, I'm not sure. Honestly, just can't seem to get volumes to work smoothly here. Database isn't persisting and then it pulls that can't connect stuff if I use a volume that was given in the example above |
Any ideas @tompropst about why I can't get
web-db
to work as a volume?After I add the
volumes
section:I get an error:
Any ideas?
The text was updated successfully, but these errors were encountered: