jenkins没有空间问题 – 在docker工人
我正在Docker里面运行Jenkins。 我收到以下空间问题。
gzip: /tmp/sbt_a74fec8a/xoquick-1.0.tar.gz: No space left on device java.lang.RuntimeException: Error gziping /tmp/sbt_a74fec8a/xoquick-1.0.tar. Exit code: 1 at scala.sys.package$.error(package.scala:27) at com.typesafe.sbt.packager.universal.Archives$.gzip(Archives.scala:93) at com.typesafe.sbt.packager.universal.Archives$$anonfun$9.apply(Archives.scala:111) at com.typesafe.sbt.packager.universal.Archives$$anonfun$9.apply(Archives.scala:111) at com.typesafe.sbt.packager.universal.Archives$$anonfun$makeTarball$1.apply(Archives.scala:136) at com.typesafe.sbt.packager.universal.Archives$$anonfun$makeTarball$1.apply(Archives.scala:118) at sbt.IO$.withTemporaryDirectory(IO.scala:285) at com.typesafe.sbt.packager.universal.Archives$.makeTarball(Archives.scala:118) at com.typesafe.sbt.packager.universal.Archives$$anonfun$10.apply(Archives.scala:111) at com.typesafe.sbt.packager.universal.Archives$$anonfun$10.apply(Archives.scala:111) at scala.Function3$$anonfun$tupled$1.apply(Function3.scala:35) at scala.Function3$$anonfun$tupled$1.apply(Function3.scala:34) at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47) at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:42) at sbt.std.Transform$$anon$4.work(System.scala:64) at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:237) at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:237) at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:18) at sbt.Execute.work(Execute.scala:244) at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:237) at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:237) at sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:160) at sbt.CompletionService$$anon$2.call(CompletionService.scala:30) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) [error] (universal:packageZipTarball) Error gziping /tmp/sbt_a74fec8a/xoquick-1.0.tar. Exit code: 1 [error] Total time: 7 s, completed Feb 5, 2015 9:41:58 AM Build step 'Build using sbt' changed build result to FAILURE Build step 'Build using sbt' marked build as failure SSH: Current build result is [FAILURE], not going to run. Finished: FAILURE
在泊坞窗我导航到/tmp
文件夹
cd /tmp/
接着
df -h . Filesystem Size Used Avail Use% Mounted on /dev/mapper/docker-253:2-18350588-5a4c880a0e55c5b8a78ca16e7ef7fbedb7559cf07b3e249f81b88809901cca72 9.9G 9.1G 316M 97% /
我有足够的空间留在里面。为什么工作失败?
我检查了这个http://www.ivankuznetsov.com/2010/02/no-space-left-on-device-running-out-of-inodes.html
inode也没有问题。有足够的inode可用。有人告诉我什么是问题?
Jenkins的工作通常会消耗更多〜300m的空间,包括所有构build的工件,上传到Docker容器的任何东西,版本控制检出的大小等等。
将其添加到root的crontab以定期清理旧的容器。 inputsudo crontab -e
来编辑:
SHELL=/bin/bash @daily (echo "Cleaning Docker images at $(date):"; docker rm $(docker ps -a -q); docker rmi $(docker images | grep '<none>' | tr -s ' ' | cut -d ' ' -f 3)) &>> /var/log/dockerClean.log
(如果你喜欢sh
,你可以用2>&1 > /var/log/dockerClean.log
replaceSHELL
行,如果你的系统默认是bash
,可以忽略它,不作任何改动)
- docker cp:没有权限在主机上创build文件夹
- 使用Ansible迭代从Docker API返回的json
- docker中的WordPress:在此服务器上未find请求的URL xxx
- Dockerfile与构build问题
- 连接问题与Docker
- “curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add – “我们应该在这里添加一些密钥?
- 令牌请求在Docker背后键入,curl工作,reactjs不
- docker-compose up“UnixHTTPConnectionPool(host ='localhost',port = None):Pool is closed”
- Docker卷装载显示一个linux目录的空目录