You can translate the question and the replies:

Mount failed in kubernetes

Now i want to persistent the whole /opt/denodo folder in kubernetes. I got error if i set mountpath as /opt/denodo. But it runs well if i set /opt/denodo/conf or /opt/denodo/logs as mountpath. I have been read this artical about deploying denodo in kubernets,but there is only configmap(license) configuration written on yaml sample. https://community.denodo.com/kb/en/view/document/Deploying%20Denodo%20in%20Kubernetes?category=Operation does anybody had same error when mounting whole /opt/denodo folder. i will be appriciate if someone could share sample code about persisting the whole /opt/denodo folder in k8s. deployment.yml ``` volumeMounts: - name: license-volume mountPath: /opt/denodo/conf/denodo.lic subPath: denodo.lic - name: solutionmanager-data-volume mountPath: /opt/denodo/ imagePullSecrets: - name: denodo-pull volumes: - name: license-volume configMap: name: sol-license - name: solutionmanager-data-volume persistentVolumeClaim: claimName: pvc-denodo-solutionmanager ``` pod error ``` Error: failed to start container "denodo-solutionmanager": Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "./denodo-container-start.sh": stat ./denodo-container-start.sh: no such file or directory: unknown ```
user
08-06-2021 05:12:48 -0400

1 Answer

Hi, Ideally, when a volume is created, it may not have any data in it. When you create the pod with the YAML as specified in the question, I suspect there would not be any data present leading to the below error because the script 'denodo-container-start.sh' cannot be found: ``` "Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "./denodo-container-start.sh": stat ./denodo-container-start.sh: no such file or directory: unknown" ``` Similarly, when you specify some other folder, then probably the pod would start but it may be broken with some missing information. In this scenario where you would like to perform mounts, I would suggest you to initialize the volume first with the required data such that files are available as expected. Please refer to the [Init Containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/) document for more details. Further, on going through the snippet from the YAML file, I believe that you are trying to mount '/opt/denodo/' as a "data volume". In general, the folder '/opt/denodo/' is the app installation volume and it is not certain that application would work as intended with the setup related to the data volume specified. I would recommend you to refer to the Knowledge Base (KB) article [Data Persistence in Containers](https://community.denodo.com/kb/en/view/document/Data%20Persistence%20in%20Containers) which would help you identify the folders which are needed to persist. For additional information, you can also check the aricle [Deploying the Denodo Solution Manager in Kubernetes](https://community.denodo.com/kb/en/view/document/Deploying%20the%20Denodo%20Solution%20Manager%20in%20Kubernetes). If you still need help and if you are a valid support user then you can raise a support case on [Denodo Support Site](https://support.denodo.com/) so that our support team can help you. Hope this helps!
Denodo Team
09-06-2021 08:10:09 -0400
You must sign in to add an answer. If you do not have an account, you can register here