Skip to main content
NetApp Knowledge Base

trident-operator fails to start with "/trident-operator: no such file or directory"

  1. Last updated
  2. Save as PDF
Views:
96
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • NetApp Astra Trident
  • Store container images in closed registry
  • During manual trident-operator deployment in offline mode

Issue

After running kubectl create -f deploy/bundle_post_1_25.yaml according to Manually deploy the Trident operator (Offline mode),  kubectl describe pod trident-operator -n trident reports error:

Warning  Failed  2m47s                 kubelet  Error: container create failed: time="2024-05-14T09:31:38Z" level=error msg="runc create failed: unable to start container process: exec: \"/trident-operator\": stat /trident-operator: no such file or directory"
Warning  Failed  2m3s (x3 over 2m31s)  kubelet (combined from similar events): Error: container create failed: time="2024-05-14T09:32:22Z" level=error msg="runc create failed: unable to start container process: exec: \"/trident-operator\": stat /trident-operator: no such file or directory"
Normal   Pulled  108s (x13 over 4m9s)  kubelet  Container image "<registry>/netapp/trident-operator:24.02.0" already present on machine

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.