-
Notifications
You must be signed in to change notification settings - Fork 200
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
docker volume plugin #54
Comments
@OXide94 that is really nice, but I was talking about something else. I was talking about Docker volume plugin, which means you can mount MooseFs in Docker image (like this https://infinit.sh/documentation/docker/volume-plugin) I am willing to help |
@karolmajek FYI |
@tivvit, oh of course you're right, I've just somehow omitted "volume" while reading your post :) |
Hi @tivvit, Thanks, |
Wow! Great job, I will try that and let you know |
Thank you for the job! I will try to test it in a few days. But after reading the README, there are some behaviors I do not understand yet, in the scenario:
In anycase I will also try to answer this in my future tests. |
@karolmajek, can you please answer @antoinetran questions? Thanks, |
Finally I was able to answer your questions @antoinetran about scenarios ScenariosIn following scenarios we are using directory In all scenarios MooseFS Docker Cluster is used: https://github.com/moosefs/moosefs-docker-cluster MooseFS should be mounted to create a volumeDirectory Preconditions
Empty directory exists: /mnt/moosefsCommand: ls -l /mnt/moosefs outputs: total 0 The result of tree /mnt/ is /mnt/ └── moosefs MooseFS is not mounted on hostCommand Expected resultError, volume should not be created Actual resultIf we will try to create a volume we will get following error: docker volume create -d moosefs --name mymoosefs -o mountpoint=/mnt/moosefs Error response from daemon: create mymoosefs: VolumeDriver.Create: Cannot create volume /mnt/moosefs as it's not a valid MooseFS mount Can't create volume when mount directory doesn't existDirectory Preconditions
Directory doesn't exist: /mnt/moosefsCommand: ls -l /mnt outputs: total 0 The result of tree /mnt is 0 directory, 0 files Expected resultError, volume should not be created Actual resultIf we will try to create a volume we will get following error: docker volume create -d moosefs --name mymoosefs -o mountpoint=/mnt/moosefs Error response from daemon: create mymoosefs: VolumeDriver.Create: Cannot create volume /mnt/moosefs as it's not a valid MooseFS mount MooseFS Client killed when volume is mountedMooseFS is mounted in /mnt/moosefs, we have a volume mapped, but we then have a MooseFs client crash Preconditions
Directory exists: /mnt/moosefsCommand: ls -l /mnt/moosefs outputs: total 0
Command mount | grep moosefs gives following result: mfsmaster:9421 on /mnt/moosefs type fuse.mfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other) The result of tree /mnt/ is /mnt/ └── moosefs └── welcome_to_moosefs.txt Docker Volume is attached to /mnt/moosefsVolume is mounted using following command: docker volume create -d moosefs --name mymoosefs -o mountpoint=/mnt/moosefs Response: mymoosefs List volumes: docker volume ls DRIVER VOLUME NAME moosefs mymoosefs Run container using volumeRun example nginx container which will mount docker run -ti -v mymoosefs:/usr/share/nginx/html -p 10080:80 nginx:latest bash -c "service nginx start;bash" MooseFS Client is killedsudo killall -9 mfsmount Expected resultActual resultIf we will try to list files in the container: (volume is mounted in /usr/share/nginx/html) ls -l /usr/share/nginx/html ls: cannot access '/usr/share/nginx/html': Transport endpoint is not connected Attempt to use subdirectory as volumeMooseFS is mounted in /mnt/moosefs, we create a container mapped to /mnt/moosefs/subdir1 that does not exist Preconditions
Directory exists: /mnt/moosefsCommand: ls -l /mnt/moosefs outputs: total 0 MooseFS is mounted in /mnt/moosefsCommand mount | grep moosefs gives following result: mfsmaster:9421 on /mnt/moosefs type fuse.mfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other) The result of tree /mnt/ is /mnt/ └── moosefs └── welcome_to_moosefs.txt /mnt/moosefs/subdir1 doesn't existList files of /mnt/moosefs/subdir1 to check if it exist: ls -l /mnt/moosefs/subdir1 ls: cannot access '/mnt/moosefs/subdir1': No such file or directory Expected resultError, volume should not be created Actual resultIf we will try to create a volume we will get following error: docker volume create -d moosefs --name mymoosefs -o mountpoint=/mnt/moosefs/subdir1 Error response from daemon: create mymoosefs: VolumeDriver.Create: Cannot create volume /mnt/moosefs/subdir1 as it's not a valid MooseFS mount No MooseFS Client on host machineMooseFS Client is installed and mounted in a container, and no MooseFS package is installed in host, and we create the container MooseFS Client is required on host machine for now, we plan to provide Docker Volume Plugin which will not need installing additional packages on host machine. The plugin will be a client for MooseFS |
Hi, do you have any plans for docker volume plugin?
It would be awesome.
The text was updated successfully, but these errors were encountered: