下面的配置在OpenKruise k8s 下apply 没有问题,怎么在cloneset 下apply 就报错呢? volumeMounts: - name: backend-conf1 mountPath: /dipeak/web-backend/conf/engine.conf subPath: engine.conf - name: backend-conf2 mountPath: /dipeak/web-backend/conf/application.properties subPath: application.properties volumes: - name: backend-conf1 configMap: name: backend-conf1 - name: backend-conf2 configMap: name: backend-conf2 这个问题可以绕过去吗?咱们的cloneset 下改怎么配置呢?Error: failed to start container "backend": Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/var/lib/kubelet/pods/80b7e911-8170-4d66-a8f5-b71344ba7fee/volume-subpaths/backend-conf2/backend/2" to rootfs at "/dipeak/web-backend/conf/application.properties": mount /var/lib/kubelet/pods/80b7e911-8170-4d66-a8f5-b71344ba7fee/volume-subpaths/backend-conf2/backend/2:/dipeak/web-backend/conf/application.properties (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
你可以比较下cloneset , 和deployment 创建的pod有什么差异。此回答整理自钉群“OpenKruise 社区交流群”
版权声明:本文内容由阿里云实名注册用户自发贡献,版权归原作者所有,阿里云开发者社区不拥有其著作权,亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容,填写侵权投诉表单进行举报,一经查实,本社区将立刻删除涉嫌侵权内容。
阿里云拥有国内全面的云原生产品技术以及大规模的云原生应用实践,通过全面容器化、核心技术互联网化、应用 Serverless 化三大范式,助力制造业企业高效上云,实现系统稳定、应用敏捷智能。拥抱云原生,让创新无处不在。