这篇博客详细记录了解决使用Jenkins部署k8s时遇到的问题，包括jenkins推送报错找不到cloud、Dockerfile不存在以及kubectl命令错误。作者通过检查配置和文件名，成功解决了这些问题。最后，作者分享了自己的技术背景和对面试的看法。
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
最低0.47元/天 解锁文章
扫一扫
319
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
