You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ok - so the fileshelter.conf is a directory - sue to the stupid docker "if you mount one thing and it doesn't exist I will assume it is a directory
Touching the file first didn't seem to work - it told me that '' was not an absolute working dir.
Got it working in the end by creating var and config as subdirs under /mnt/fileshelter and then mapping var to var and the conf file to config/fileshelter.conf but only after copying the fileshelter.conf as supplied from the docker container, putting it at the right place and 777 permissions.
I am sure it could be simplified but my head hurts and it works.
I almost seems that the conf file needs to be read before the stuff is created the first time for the container (which would be bonkers)
Life would be so much easier is all the stuff that needed to be exposed was in one directory in the docker image.
I created the docker container running as fileshelter:fileshelter
Create a user filehshelter:fileshelter on host
Created /mnt/fileshelter on host (777 to get it to work)
Bind volumes set as:
What I get in /mnt/fileshelter is:
Erm - what is going on. We have the conf file owner by root and the others owned by postfix
I though they would all be owned by fileshelter.
Will this work if I upload files since postfix owns that dir.
Confused as to what should happen and why this is happening.
The text was updated successfully, but these errors were encountered: