几个节点可以访问安装的Docker容器 [英] Can several nodes access mounted docker containers

查看:298
本文介绍了几个节点可以访问安装的Docker容器的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述



如果我将/ var / lib / docker移动到/ mnt / containers /,其中/ mnt / containers
通过glusterfs加载到一个较大的系统,我开始收到这样的错误:

  kernel@192.168 .68.14:Jun 17 16:05:10 stackato-ft9y kernel:[2174.535122] aufs au_xino_set:1176:docker [7572]:I / O错误,创建xino失败(-27)。 

kernel@192.168.68.14:Jun 17 16:05:10 stackato-ft9y kernel:[2174.538613] aufs au_xino_set:1176:docker [7572]:I / O错误,创建xino失败(-27 )。

dockerd@192.168.68.14:[error] mount.go:11 [warning]:在卸载之前无法运行auplink:exit status 22 ^ M

dockerd@192.168 .68.14:文件太大

dockerd@192.168.68.14:[d954f89b] -job create(fence_app_staging_fibo_1a992a98_id-3dd68)= ERR(1)^ M

dockerd@192.168。 68.14:[error] server.go:1025错误:文件太大^ M

dockerd@192.168.68.14:[error] server.go:90 HTTP错误:statusCode = 500文件太大

在/ var / lib / docker运行时,我看不到这些错误,即使我移动/ var / lib / docker的
内容到不同的本地目录。



我们中的两个人独立地绊倒了 http://osdir.com/ml/linux.file-systems.aufs.user/ 2008-08 / msg00016.html ,但是看起来不是很正确。所以我在这里希望得到驻地码头/ aufs / glusterfs专家的关注。

解决方案

看起来像aufs和glusterfs。您是否尝试使用btrfs或devicemapper? (使用 -s btrfs -s devicemapper 启动守护程序)


I have a VM running an app that uses about 8 Docker containers.

If I move /var/lib/docker to /mnt/containers/, where /mnt/containers is mounted via glusterfs to a larger system, I start getting errors like this:

kernel@192.168.68.14: Jun 17 16:05:10 stackato-ft9y kernel: [ 2174.535122] aufs au_xino_set:1176:docker[7572]: I/O Error, failed creating xino(-27).

kernel@192.168.68.14: Jun 17 16:05:10 stackato-ft9y kernel: [ 2174.538613] aufs au_xino_set:1176:docker[7572]: I/O Error, failed creating xino(-27).

dockerd@192.168.68.14: [error] mount.go:11 [warning]: couldn't run auplink before unmount: exit status 22^M

dockerd@192.168.68.14: file too large

dockerd@192.168.68.14: [d954f89b] -job create(fence_app_staging_fibo_1a992a98_id-3dd68) = ERR (1)^M

dockerd@192.168.68.14: [error] server.go:1025 Error: file too large^M

dockerd@192.168.68.14: [error] server.go:90 HTTP Error: statusCode=500 file too large

I don't see these errors when running out of /var/lib/docker, or even if I move the contents of /var/lib/docker to a different local directory.

Two of us have independently stumbled on http://osdir.com/ml/linux.file-systems.aufs.user/2008-08/msg00016.html , but that doesn't quite look right. So I'm here hoping to get the attention of the resident docker/aufs/glusterfs experts.

解决方案

Looks like conflict between aufs and glusterfs. Have you tried to use btrfs or devicemapper instead? (start the daemon with -s btrfs or -s devicemapper)

这篇关于几个节点可以访问安装的Docker容器的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆