Description of problem: Docker container fails to start and reports back VolumeDriver.Mount error Version-Release number of selected component (if applicable): Docker v1.10 MongoDB v3.2 How reproducible: Every time. Steps to Reproduce: 1. Install latest version of Docker 2. Pull MongoDB v3.2.6 from Docker public repo 3. docker run --volume-driver=glusterfs --volume=mongo:/data/db mongo_docker_image Actual results: Container starts up and fails Expected results: Container to run using glusterfs plugin Additional info: Works fine when rolling back to MongoDB v2.6. This issue could be related to the storage engine changes in v3.
Please attach all the glusterfs related logs.
Created attachment 1179312 [details] glusterfs log
Hello, just checking in to see if there have been any updates or any additional info needed. Thank you.
(In reply to chris.mitchell from comment #2) > Created attachment 1179312 [details] > glusterfs log I see only the mount log attached here. You'd need to provide all the client, brick and glusterd log files to help us in analysing the issue.
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days