问题描述

Jenkins构建项目时报错，错误信息：

Docker Build
Docker Build: building image at path /opt/jenkins/workspace/测试环境发布（docker）/xxx/xxx/xxx
ERROR: Build step failed with exception
com.github.dockerjava.api.exception.InternalServerErrorException: {"message":"Error processing tar file(exit status 1): write /target/classes/log4jdbc.log4j2.properties: no space left on device"}at com.github.dockerjava.netty.handler.HttpResponseHandler.channelRead0(HttpResponseHandler.java:109)at com.github.dockerjava.netty.handler.HttpResponseHandler.channelRead0(HttpResponseHandler.java:33)at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)at io.netty.handler.logging.LoggingHandler.channelRead(LoggingHandler.java:241)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:438)at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:323)at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:297)at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:253)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1432)at io.netty.handler.ssl.SslHandler.decodeJdkCompatible(SslHandler.java:1199)at io.netty.handler.ssl.SslHandler.decode(SslHandler.java:1243)at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:502)at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:441)at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:278)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965)at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:648)at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:583)at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:500)at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:462)at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:897)at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)at java.lang.Thread.run(Thread.java:748)
Build step 'Build / Publish Docker Image' marked build as failure
Finished: FAILURE

原因分析：

Jenkins打包的机器或者部署项目的机器，磁盘满了所导致。

解决方案：

1.查看磁盘占用情况

df -h

2.删除没有在用的镜像和容器

docker system prune

输入：y 回车

查看效果

3.查找当前目录每个文件夹大小

du -h --max-depth=1

删掉一些没用的东西，优化磁盘空间

Jenkins构建项目时报错“message“:“Error processing tar file(exit status 1): write/xxx/no space left on device相关推荐

failed to register layer: Error processing tar file(exit status 1): archive/tar: invalid tar header
网上通用解法: 保存镜像时: docker save -o [image].tar // 重点是加上-o选项 load镜像时: docker load -i [image].tar https ...
dockerError processing tar file(exit status 1): no space left on device
问题:空间不够问题描述: Error processing tar file(exit status 1): no space left on device 解决方案: 查询默认路径为 /var/l ...
docker加载镜像报错 dockerError processing tar file(exit status 1): no space left on device
问题描述: 在运行docker load 加载镜像时报错 dockerError processing tar file(exit status 1): no space left on device ...
关于编译QT项目时报错： error: cannot find -lGL 的解决方法
若该文为原创文章,转载请注明原文出处本文章博客地址:https://hpzwl.blog.csdn.net/article/details/78260169 红胖子(红模仿)的博文大全:开发技术集合 ...
jenkins构建项目报错：java:[17,37] package xx.xx.xxx does not exist
场景描述今天遇到了一个很奇怪的问题,在IDEA运行正常的项目,发布到jenkins就会报错: [ERROR] COMPILATION ERROR : [INFO] ----------------- ...
spring boot: 构建项目时报错Not a managed type
今天在学习使用Spring Data JPA的时候,将bean和JpaRepository放在了不同的package中,导致无法构建项目,报以下错误: org.springframework.bean ...
Linux编译QT项目时报错： error: cannot find -lGL 的解决方法
错误: 编译qt项目的时候出现错误:error: cannot find -lGL 错误产生原因: 无法找到-lGL,-l表示库文件,根据QT的库规则,可以得到该库的名称: libGL.so 解决方法 ...
vscode创建新的Vue项目时报错Parsing error: No Babel config file detected for ......
原因: 项目未找到babel.config.js文件,此时项目的根目录并使项目本身,因此报错,如下图: 解决:项目根目录只要是项目本身即可解决,如下图:
运行Springboot项目时报错WhiteLabel Error Page
问题描述 ![在这里插入图片描述](https://img-blog.csdnimg.cn/img_convert/1feaee05fe34bfb4049b19860fef1773.png 解决方案: ...

Jenkins构建项目时报错“message“:“Error processing tar file(exit status 1): write/xxx/no space left on device

文章目录

推荐文章

问题描述

原因分析：

解决方案：

1.查看磁盘占用情况

2.删除没有在用的镜像和容器

3.查找当前目录每个文件夹大小

Jenkins构建项目时报错“message“:“Error processing tar file(exit status 1): write/xxx/no space left on device相关推荐

最新文章

热门文章