{"id":1048,"date":"2014-02-16T08:27:30","date_gmt":"2014-02-16T08:27:30","guid":{"rendered":"http:\/\/wp.neependra.net\/?p=1048"},"modified":"2014-02-16T08:27:30","modified_gmt":"2014-02-16T08:27:30","slug":"running-glusterfs-inside-docker","status":"publish","type":"post","link":"https:\/\/neependra.net\/index.php\/2014\/02\/16\/running-glusterfs-inside-docker\/","title":{"rendered":"Running GlusterFS inside docker container"},"content":{"rendered":"

As a part of GlusterFS 3.5 testing and hackathon<\/a>, I decided to put GlusterFS<\/a> inside a docker container<\/a>.So I installed docker on my Fedora20 desktop<\/p>\n

[sourcecode language=”text” gutter=”false”]
\n$ yum install docker-io -y
\n$ systemctl enable docker.service
\nln -s ‘\/usr\/lib\/systemd\/system\/docker.service’ ‘\/etc\/systemd\/system\/multi-user.target.wants\/docker.service’
\n$ systemctl start docker.service
\n$ docker version
\nClient version: 0.7.6
\n..
\nServer version: 0.7.6
\n[\/sourcecode]<\/p>\n

and then started a Fedora container<\/p>\n

[sourcecode language=”text” gutter=”false”]
\n$ docker run -i -t mattdm\/fedora \/bin\/bash
\n[\/sourcecode]<\/p>\n

Once I am inside the container I installed GlusterFS packages<\/p>\n

[sourcecode language=”text” gutter=”false”]
\nbash-4.2# yum install glusterfs glusterfs-server -y
\n[\/sourcecode]<\/p>\n

And then tried to create volume<\/p>\n

[sourcecode language=”text” gutter=”false”]
\nbash-4.2# \/usr\/sbin\/glusterd
\nbash-4.2# gluster volume create vol 172.17.0.3:\/mnt\/brick\/ force
\n[\/sourcecode]<\/p>\n


\nbut I got following error:-
\n<\/span><\/p>\n

[sourcecode language=”text” gutter=”false”]
\nvolume create: vol: failed: Glusterfs is not supported on brick: 172.17.0.3:\/mnt\/brick.
\nSetting extended attributes failed, reason: Operation not permitted.
\n[\/sourcecode]<\/p>\n

From above error it looked as setting up extended attributes are not supported, which is a basic need to use GlusteFS. So I tried to test them manually. I was able to set extended attributes in user<\/em> namespace but not in trusted<\/em> namespace.<\/p>\n

[sourcecode language=”text” gutter=”false”]
\nbash-4.2# yum install attr -y
\nbash-4.2# setfattr -n user.foo1 -v "bar" a
\nbash-4.2# touch a; setfattr -n trusted.foo1 -v "bar" a
\nsetfattr: a: Operation not permitted
\n[\/sourcecode]<\/p>\n

With some internet search I figured out that CAP_SYS_ADMIN<\/strong> is needed for setting up extended attributes in trusted<\/em> namespace and to get that inside docker we need to run an image with –privileged=true<\/em> option like<\/span><\/p>\n

[sourcecode language=”text” gutter=”false”]
\n$ docker run –privileged=true -i -t mattdm\/fedora \/bin\/bash
\n[\/sourcecode]<\/p>\n

With that I was able to create the volume and start it<\/p>\n

[sourcecode language=”text” gutter=”false”]
\nbash-4.2# gluster volume create vol 172.17.0.3:\/mnt\/brick\/ force
\nbash-4.2# gluster volume start vol
\n[\/sourcecode]<\/p>\n

But when I tried to mount the volume I got following error:-<\/p>\n

[sourcecode language=”text” gutter=”false”]
\nE [mount.c:267:gf_fuse_mount] 0-glusterfs-fuse: cannot open \/dev\/fuse (No such file or directory)
\n[\/sourcecode]<\/p>\n

this turned out to be image specific problem, which I am using (mattdm\/fedora). I had to mknod for \/dev\/fuse<\/em><\/p>\n

[sourcecode language=”text” gutter=”false”]
\nbash-4.2# mknod \/dev\/fuse c 10 229
\n[\/sourcecode]<\/p>\n

and after that I was able to mount volume.<\/p>\n

On Fedroa 20 for docker version 0.7.6 the default storage driver for docker is device-mapper on which extended attributes are supported. AUFS storage driver does not support extended attributes as of now.I\u00a0have tried with btrfs<\/em> storage driver with docker 0.8 as well and was able to use GlusterFS. To use btrfs\u00a0<\/em>storage driver, we need to start docker daemon with following command :-<\/p>\n

[sourcecode language=”text” gutter=”false”]
\n$ docker -d -s btrfs
\n[\/sourcecode]<\/p>\n

Above will only work if Docker is running on a btrfs<\/em> partition already prepared by the host system.<\/p>\n","protected":false},"excerpt":{"rendered":"

As a part of GlusterFS 3.5 testing and hackathon, I decided to put GlusterFS inside a docker container.So I installed docker on my Fedora20 desktop [sourcecode language=”text” gutter=”false”] $ yum install docker-io -y $ systemctl enable docker.service ln -s ‘\/usr\/lib\/systemd\/system\/docker.service’ ‘\/etc\/systemd\/system\/multi-user.target.wants\/docker.service’ $ systemctl start docker.service $ docker version Client version: 0.7.6 .. Server version: 0.7.6 … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[18,24,25,29,41,42],"tags":[65,70,81,84,90,91,107,125],"class_list":["post-1048","post","type-post","status-publish","format-standard","hentry","category-docker","category-geek","category-gluster","category-learning","category-redhat","category-rhs","tag-btrfs","tag-container","tag-docker","tag-fedora","tag-geek","tag-glusterfs","tag-linux","tag-redhat"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t