-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Server Errors when trying to bind mount docker volume #132
Comments
Hey @TadeSF, thx for opening this issue. First, are you running this on Linux or Mac/Windows? The issue I found is the following, the storage folder inside the image contains a directory structure that needs to exist for the app to work. Usually, the expected behavior would be that on first mount, the volume is populated with the container contents. This is what happens if you are using named volumes, for example. Since on Mac / Windows Docker is running inside a Virtual Machine, there might be problems with this behavior? I also just tested it on MacOS. If you are indeed on a Linux machine, I will further test this. The best solution right now would be to use a named volume and then backup this named volume? |
I too am getting this, on Linux. Using named volumes is not an option for me, as I require all data to be stored in a local directory for my Docker containers (I am using a server where the Docker volumes may be cleared). It seems that the mounted directory is not being populated. The error on request:
|
Hello. Is there any update on this? This is really needed in certain docker deployments. |
@anarion80 no solution yet. The problem is that the application is unable to create the folder structure in the volume. If you guys have to suggestions on how to tackle this, I appreciate it. I thought about adding a script for the case where you can not use named volumes, that runs on startup and creates the folder structure inside the mounted path. But not sure if this is the right way to go. |
Hey @PhilReinking! You already have a
The script inside the container should have all necessary execution rights thanks to these lines already in the Docker-Compose:
And if I understand Docker correctly, Docker should create the files on the mounted volume with ownership of the configured Docker-User (e.g. Btw. sorry for being so unresponsive after submitting the issue – i lost track of it and just now stumbled over the notification 😅 |
Hey there!
I tried to setup input and I got it working so far. Altough I ran into the same issue raised in #131 today too when trying to add new teammembers, I have a different problem when it comes to docker volumes.
When I create a docker-volume like this ...
... I have no issue. However, when I try to bind mount the volume to my persisted/backed-up storage directory, I get weird errors in the logs, no matter what I try with ownership and permissions and creating the folders and database in advance and/or not... Since storing the data within my persisted path would make my backup-life much easier, I decided to raise this issue.
I got sometimes got different errors, but when I try it like this with no preexisting folder-structure or data without any modification like this ...
... I first get somewhat successful logs ...
... but when I try to access the webpage, I get these errors:
I understand that this must be related to permissions somehow since it works perfectly in a not bind mounted volume. But still whatever I tried, I got (sometimes slightly different) error messages of missing files...
I hope you can help – apart from this I am really enjoying input! If you need any further Info or if I can help in any way, please let me know.
Thanks and all the best,
Tade
The text was updated successfully, but these errors were encountered: