ERROR: for plain-docker-nfsmount_api_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: for api UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
I think itās related to the image I use (which is devwithlando/php:7.1-apache). This is my docker-compose.yml:
Does anyone have a reference to any documentation about this?
Except for the laconic release note āSupport NFS Volume sharingā itās as if this doesnāt exist.
It may be the same issue we have in Windows where there is a race condition of the share drive not connected yet before the containers start up.
Could you explain this a bit more? Iām having an issue like this with the NFS native support on Mac. I need the shared directory (the root of the docker4drupal repo, which has docker-compose.yml and such) to be shared with a php container and an nginx container. But the php container never comes up, which takes down the nginx container with it.
Iām not sure what NFS options would be needed for a php-fpm based container and an nginx container to share the same NFS share. But this does not appear to work:
@seanhandley - I remember I saw you comment something about nfsv4, not sure whereā¦
Any chance you remember how you managed to get it working with nfsv4?
When I try I get this error: āprotocol not supportedā when using ānfsvers=4ā, ānfsvers=4.1ā and āvers=4ā
Also, do you remember what seemed more stable with nfsv3? Iām actually trying to move to v4 to see if it improves performance, mainly around deleting many files and also how nfsv3 implements the āsilly renameā (causing āāDevice or resource busyā errors on random .nfsXXXXXā files)
ok, tks for sharing!
I will play around with the acregmin and acdirmin attributes, those might actually solve some (rare) cases where users have seen stale files.
In general, this solution has been running fine for us for a while now (developing jvm projects with bazel, where bazel is run inside a container)
When I try to bring up my containers, docker-compose is telling me:
ERROR: for docker_php_1 Cannot start service php: error while mounting volume ā/var/lib/docker/volumes/docker_wordpress/_dataā: error while mounting volume with options: type=ānfsā device=ā:/Volumes/Drobo/src/megbitton_com/docker/wordpressā o=āaddr=localhost,rwā: operation not supported
Furthermore, I can mount that NFS share locally on my Mac using either sudo mount from the command line or using the Finderās Connect to Server dialog. Any ideas what might be missing? Iām defining the volume in my compose file as such
volumes:
wordpress:
driver: local
driver_opts:
device: ā:/Volumes/Drobo/src/megbitton_com/docker/wordpressā
o: addr=localhost,rw
type: nfs
and for the service
volumes:
ā wordpress:/code
Thanks for your info here, I am still facing this issue (Permission denied), I have copy pasted everything as you have mentioned in this page, Yet I am facing the permission issue, When I executed āshowmount -eā I am getting empty results ( It just says "Exports list on localhost: " ).
failed to mount local volume: mount :/Users/santhu/docker:/var/lib/docker/volumes/docker_nfsmount/_data, data: addr=192.168.65.2,nolock,hard,nointr,nfsvers=3: permission denied
when I do cat /etc/exports file : I can see below info
/Users -alldirs -mapall=502:20 localhost
Not sure what the problem is, But I am struggling with this error from past one week, Would you mind suggesting what went wrong here? Thanks in advance.
Unfortunately the nature of my job has changed and Iām not working with docker config issues any more. Iād like to tell you I could commit to helping fix this in my spare time but Iām at home in lockdown with my family and āspare timeā is an alien concept right now!
Hope you can figure it out, or get some help from someone else on the forum.