Step 3/5 : ADD index.html /usr/share/nginx/html/
—> 98bf97f66da4
Step 4/5 : EXPOSE 80
—> Running in 608233613a02
Removing intermediate container 608233613a02
—> c2ece88c90fd
Step 5/5 : ENTRYPOINT nginx -g “daemon off;”
—> Running in 92673c1fde3d
Removing intermediate container 92673c1fde3d
—> 9883d2c3505c
Successfully built 9883d2c3505c
Tagging built image with 192.168.59.151:5000/cka/nginx:10
Docker Build Response : 9883d2c3505c
Pushing [192.168.59.151:5000/cka/nginx:10]
The push refers to repository [192.168.59.151:5000/cka/nginx]
21d587650c44: Preparing
075508cf8f04: Preparing
5c865c78bc96: Preparing
134e19b2fac5: Preparing
83634f76e732: Preparing
766fe2c3fc08: Preparing
02c055ef67f5: Preparing
766fe2c3fc08: Waiting
02c055ef67f5: Waiting
83634f76e732: Layer already exists
134e19b2fac5: Layer already exists
5c865c78bc96: Layer already exists
075508cf8f04: Layer already exists
766fe2c3fc08: Layer already exists
02c055ef67f5: Layer already exists
21d587650c44: Pushing [==================================================>] 512B
21d587650c44: Pushing [==================================================>] 4.096kB
21d587650c44: Pushed
10: digest: sha256:56aec690ee246fd8c4beded0146027977fcbb3a8a4e0bd6a84c73e235b6bce7e size: 1777
Docker Build Done
[p1] $ /bin/sh -xe /tmp/jenkins1779175233576847412.sh
-
export KUBECONFIG=/admin.conf
-
KUBECONFIG=/admin.conf
-
/kubectl set image deployment/web1 nginx=192.168.59.151:5000/cka/nginx:10 -n safe
deployment.apps/web1 image updated
Finished: SUCCESS
jenkins推送报错Could not find the cloud this project was built on
- 此时其实gitlab是推送成功了的,因为代码推送以后,容器家目录总已经有我定义的内容和DockerFile文件了
[root@a2b493904798 jenkins_home]# cd p1
[root@a2b493904798 p1]# ls
DockerFile index.html
[root@a2b493904798 p1]# cat index.html
ccxhero_20211112
[root@a2b493904798 p1]# pwd
/var/jenkins_home/p1
[root@a2b493904798 p1]#
- 单纯的是因为jenkins推送失败了
报错内容如下
Started by remote host 172.17.0.1
Running as SYSTEM
Building in workspace /var/jenkins_home/workspace/p1
[p1] $ /bin/sh -xe /tmp/jenkins1698812233066315197.sh
-
cd /var/jenkins_home
-
rm -rf p1
-
git clone http://192.168.59.151/root/p1.git
Cloning into ‘p1’…
ERROR: Build step failed with exception
java.lang.RuntimeException: Could not find the cloud this project was built on
at com.nirima.jenkins.plugins.docker.builder.DockerBuilderPublisher.getDockerAPI(DockerBuilderPublisher.java:259)
at com.nirima.jenkins.plugins.docker.builder.DockerBuilderPublisher.perform(DockerBuilderPublisher.java:451)
at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:112)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1894)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:428)
Build step ‘Build / Publish Docker Image’ marked build as failure
Finished: FAILURE
-
解决
-
看下上面
继续构建1
中的3中是不是没选择为docker -
上报报错呢,我是把jenkins的p1项目删了重新创建的【啥配置内容都没变】
-
然后把kc1文件换成admin.conf了【猜想是kc1的权限出问题了】
-
不知道是上面哪个生效的,反正是做了上面2个操作
jenkins推送报错Dockerfile /var/jenkins_home/p1/Dockerfile does not exist
- 此时其实gitlab是推送成功了的,因为代码推送以后,容器家目录总已经有我定义的内容和DockerFile文件了
[root@a2b493904798 jenkins_home]# cd p1
[root@a2b493904798 p1]# ls
DockerFile index.html
[root@a2b493904798 p1]# cat index.html
ccxhero_20211112
[root@a2b493904798 p1]# pwd
/var/jenkins_home/p1
[root@a2b493904798 p1]#
- 单纯的是因为jenkins推送失败了
报错内容如下
Started by user administrator
Running as SYSTEM
Building in workspace /var/jenkins_home/workspace/p1
[p1] $ /bin/sh -xe /tmp/jenkins3778543137998925948.sh
-
cd /var/jenkins_home
-
rm -rf p1
-
git clone http://192.168.59.151/root/p1.git
Cloning into ‘p1’…
Docker Build
Docker Build: building image at path /var/jenkins_home/p1
ERROR: Build step failed with exception
java.lang.IllegalStateException: Dockerfile /var/jenkins_home/p1/Dockerfile does not exist
at com.github.dockerjava.core.dockerfile.Dockerfile.(Dockerfile.java:37)
at com.nirima.jenkins.plugins.docker.builder.DockerBuilderPublisher$DockerBuildCallable.invoke(DockerBuilderPublisher.java:437)
at com.nirima.jenkins.plugins.docker.builder.DockerBuilderPublisher$DockerBuildCallable.invoke(DockerBuilderPublisher.java:434)
at hudson.FilePath.act(FilePath.java:1076)
at hudson.FilePath.act(FilePath.java:1059)
at com.nirima.jenkins.plugins.docker.builder.DockerBuilderPublisher$Run.buildImage(DockerBuilderPublisher.java:352)
at com.nirima.jenkins.plugins.docker.builder.DockerBuilderPublisher$Run.run(DockerBuilderPublisher.java:310)
at com.nirima.jenkins.plugins.docker.builder.DockerBuilderPublisher.perform(DockerBuilderPublisher.java:451)
at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:112)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1894)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:428)
Build step ‘Build / Publish Docker Image’ marked build as failure
Finished: FAILURE
- 解决
这个报错很明显,文件名错误,主机上的Dockerfile文件不存在【文件名必须是这个名称】,我是之前拍错的时候把文件名改了。
下面是正确的文件格式。
[root@ciserver p1]# pwd
/root/p1
[root@ciserver p1]# ls
Dockerfile index.html
[root@ciserver p1]# cat Dockerfile
FROM nginx
MAINTAINER ccx
ADD index.html /usr/share/nginx/html/
EXPOSE 80
ENTRYPOINT nginx -g “daemon off;”
[root@ciserver p1]#
jenkins推送报错Error: unknown command “set” for “kubectl”
- 至此呢,已经到最后阶段了,就是重新生成pod,但是在容器中呢发现没有kubectl set这个命令
报错如下
02c055ef67f5: Pushing [==================================================>] 70.42MB
02c055ef67f5: Pushing [==================================================>] 71.5MB
02c055ef67f5: Pushing [==================================================>] 72.53MB
先自我介绍一下,小编13年上海交大毕业,曾经在小公司待过,也去过华为、OPPO等大厂,18年进入阿里一直到现在。
深知大多数初中级Java工程师,想要提升技能,往往是自己摸索成长或者是报班学习,但对于培训机构动则近万的学费,着实压力不小。自己不成体系的自学效果低效又漫长,而且极易碰到天花板技术停滞不前!
因此收集整理了一份《Java开发全套学习资料》送给大家,初衷也很简单,就是希望能够帮助到想自学提升又不知道该从何学起的朋友,同时减轻大家的负担。
由于文件比较大,这里只是将部分目录截图出来,每个节点里面都包含大厂面经、学习笔记、源码讲义、实战项目、讲解视频
如果你觉得这些内容对你有帮助,可以扫码领取!
结语
小编也是很有感触,如果一直都是在中小公司,没有接触过大型的互联网架构设计的话,只靠自己看书去提升可能一辈子都很难达到高级架构师的技术和认知高度。向厉害的人去学习是最有效减少时间摸索、精力浪费的方式。
我们选择的这个行业就一直要持续的学习,又很吃青春饭。
虽然大家可能经常见到说程序员年薪几十万,但这样的人毕竟不是大部份,要么是有名校光环,要么是在阿里华为这样的大企业。年龄一大,更有可能被裁。
送给每一位想学习Java小伙伴,用来提升自己。
本文到这里就结束了,喜欢的朋友可以帮忙点赞和评论一下,感谢支持!
-community.csdnimg.cn/images/e5c14a7895254671a72faed303032d36.jpg" alt=“img” style=“zoom: 33%;” />
结语
小编也是很有感触,如果一直都是在中小公司,没有接触过大型的互联网架构设计的话,只靠自己看书去提升可能一辈子都很难达到高级架构师的技术和认知高度。向厉害的人去学习是最有效减少时间摸索、精力浪费的方式。
我们选择的这个行业就一直要持续的学习,又很吃青春饭。
虽然大家可能经常见到说程序员年薪几十万,但这样的人毕竟不是大部份,要么是有名校光环,要么是在阿里华为这样的大企业。年龄一大,更有可能被裁。
送给每一位想学习Java小伙伴,用来提升自己。
[外链图片转存中…(img-onehK1hH-1711475349833)]
本文到这里就结束了,喜欢的朋友可以帮忙点赞和评论一下,感谢支持!
需要更多Java资料的小伙伴可以帮忙点赞+关注,点击传送门,即可免费领取!