Closed bat79a closed 6 years ago
It definitely seems like it's permissions related. Just because it's 777
, I don't think that means you can do a chown
. You may need to figure out who your Docker user is (i.e., did you set up a dedicated docker
user?) and make sure he (or she) is the owner (or in the group) of the folders.
Thx a lot, sure this is certainly my mistake ! I Will try this monday morning.
Thx again and have a good week-end.
Closing for inactivity.
Hi.
My config use a VM with doker and an other VM with NFS packages.
My container works well with this config :
Inside the folder media I have a new folder uploads with my files created when I upload some images.
if I change for this one (inspired by your example) :
I have this error :
A folder uploads is created in my host (and NFS server) inside the media folder, the docker volume is created, but the container is not running due to this error.
All folders have chmod 777 for the test.
Thx a lot.
Config :
local-persist installation was made with curl -fsSL https://raw.githubusercontent.com/CWSpear/local-persist/master/scripts/install.sh | sudo bash