码头工人建造说空间不足但有足够的空间

时间:2017-09-27 20:50:04

标签: docker

我刚刚安装了docker版本17.06.2-ee-3,在Red Hat 7.4版本上构建了915cbaa。当我尝试构建一个图像时,即使剩下足够的空间,它也会失败No space left on device。我发现这篇文章:https://jpetazzo.github.io/2014/01/29/docker-device-mapper-resize/可能不再适用了,但无论如何我都遵循了它,现在docker info显示:

 Data Space Used: 30.68GB
 Data Space Total: 268.4GB
 Data Space Available: 134.7GB
 Metadata Space Used: 32.23MB
 Metadata Space Total: 2.147GB
 Metadata Space Available: 2.115GB

我可以使用Docker版本1.7.1,构建786b29d以及带有docker版本1.11.1的Red Hat 7.2,构建5604cbe,使用Red Had 6.7成功构建相同的映像。

根据要求:

$ df -Thi
Filesystem                      Type     Inodes IUsed IFree IUse% Mounted on
/dev/mapper/rhel-root           xfs         87M  180K   87M    1% /
devtmpfs                        devtmpfs    16M  1.3K   16M    1% /dev
tmpfs                           tmpfs       16M     1   16M    1% /dev/shm
tmpfs                           tmpfs       16M  1.4K   16M    1% /run
tmpfs                           tmpfs       16M    16   16M    1% /sys/fs/cgroup
/dev/sda3                       xfs        250K   337  250K    1% /boot
/dev/mapper/vg_lvm1-elucid_vol1 ext4        47M    11   47M    1% /elucid
/dev/mapper/rhel-home           xfs         97M   16K   97M    1% /home
192.168.10.5:/projects          nfs4       625M  6.4M  619M    2% /projects
192.168.10.5:/home              nfs4       3.8M  174K  3.6M    5% /home_bekku
tmpfs                           tmpfs       16M    10   16M    1% /run/user/42
tmpfs                           tmpfs       16M     1   16M    1% /run/user/1000
tmpfs                           tmpfs       16M     1   16M    1% /run/user/522

$ df -H /var/lib/docker/
Filesystem             Size  Used Avail Use% Mounted on
/dev/mapper/rhel-root  187G   52G  135G  28% /

$ du -sH .
7990180 .

为了回应Tarun Lalwani在journalctl -f -n10运行Sep 28 08:11:38 liszt NetworkManager[2449]: <info> [1506600698.9768] device (veth1cb0d8c): link connected Sep 28 08:11:38 liszt NetworkManager[2449]: <info> [1506600698.9770] device (docker0): link connected Sep 28 08:11:39 liszt kernel: docker0: port 1(veth1cb0d8c) entered disabled state Sep 28 08:11:39 liszt kernel: docker0: port 1(veth1cb0d8c) entered disabled state Sep 28 08:11:39 liszt avahi-daemon[2350]: Withdrawing workstation service for vethb5fa5c3. Sep 28 08:11:39 liszt kernel: device veth1cb0d8c left promiscuous mode Sep 28 08:11:39 liszt kernel: docker0: port 1(veth1cb0d8c) entered disabled state Sep 28 08:11:39 liszt avahi-daemon[2350]: Withdrawing workstation service for veth1cb0d8c. Sep 28 08:11:39 liszt libvirtd[3357]: 2017-09-28 12:11:39.606+0000: 3357: error : virNetDevSendEthtoolIoctl:2939 : ethtool ioctl error: No such device Sep 28 08:11:39 liszt NetworkManager[2449]: <info> [1506600699.6083] manager: (vethb5fa5c3): new Veth device (/org/freedesktop/NetworkManager/Devices/50) Sep 28 08:11:39 liszt NetworkManager[2449]: <info> [1506600699.6110] device (veth1cb0d8c): released from master device docker0 Sep 28 08:11:39 liszt libvirtd[3357]: 2017-09-28 12:11:39.611+0000: 3357: error : virNetDevSendEthtoolIoctl:2939 : ethtool ioctl error: No such device Sep 28 08:11:39 liszt libvirtd[3357]: 2017-09-28 12:11:39.613+0000: 3357: error : virNetDevSendEthtoolIoctl:2939 : ethtool ioctl error: No such device Sep 28 08:11:39 liszt libvirtd[3357]: 2017-09-28 12:11:39.615+0000: 3357: error : virNetDevSendEthtoolIoctl:2939 : ethtool ioctl error: No such device Sep 28 08:11:39 liszt libvirtd[3357]: 2017-09-28 12:11:39.617+0000: 3357: error : virNetDevSendEthtoolIoctl:2939 : ethtool ioctl error: No such device Sep 28 08:11:39 liszt libvirtd[3357]: 2017-09-28 12:11:39.619+0000: 3357: error : virNetDevSendEthtoolIoctl:2939 : ethtool ioctl error: No such device Sep 28 08:11:39 liszt libvirtd[3357]: 2017-09-28 12:11:39.621+0000: 3357: error : virNetDevSendEthtoolIoctl:2939 : ethtool ioctl error: No such device Sep 28 08:11:39 liszt libvirtd[3357]: 2017-09-28 12:11:39.623+0000: 3357: error : virNetDevSendEthtoolIoctl:2939 : ethtool ioctl error: No such device Sep 28 08:11:39 liszt kernel: XFS (dm-5): Unmounting Filesystem 的请求,这是我收到空间信息时的输出:

force_basic_auth: True

任何人都知道如何解决这个问题,并且实际上在这里使用docker?

1 个答案:

答案 0 :(得分:3)

我终于解决了这个问题。在构建图像时使用trigger AutoConvert on Lead (after update) { list<Lead> LeadsToConvert = new list<Lead>(); for(Lead myLead: Trigger.new){ if(!myLead.isConverted && myLead.API_Convert__c == true) LeadsToConvert.add(myLead); } list<Database.LeadConvert> leadConverts = new list<Database.LeadConvert>(); for(Lead myLead : LeadsToConvert){ Database.LeadConvert lc = new database.LeadConvert(); lc.setLeadId(myLead.Id); lc.convertedStatus = 'Qualified'; //Database.ConvertLead(lc,true); lc.setDoNotCreateOpportunity(true); leadConverts.add(lc); } if(!leadConverts.isEmpty()){ for(Integer i = 0; i <= leadConverts.size()/100 ; i++){ list<Database.LeadConvert> tempList = new list<Database.LeadConvert>(); Integer startIndex = i*100; Integer endIndex = ((startIndex+100) < leadConverts.size()) ? startIndex+100: leadConverts.size(); for(Integer j=startIndex;j<endIndex;j++){ tempList.add(leadConverts[j]); } Database.LeadConvertResult[] lcrList = Database.convertLead(tempList, false); for(Database.LeadConvertResult lcr : lcrList) System.assert(lcr.isSuccess()); } } } ,我看到docker安装了一个10G的分区,里面装满了。我无法找到如何增加它,我与docker的某个人交谈,他告诉我把这些设置放在/etc/docker/daemon.json文件中:

watch df -h

在我这样做并重新启动docker之后,挂载的分区是20G,我可以构建我的图像。