runtime-operator: CrashLoopBackOff

[if0ne]

Hi there!

I have performed the following steps:

1. make kind-setup
2. make helm-install
3. kubectl get pods -l app.kubernetes.io/instance=operator-dev -n wasmcloud-system

NAME                                         READY   STATUS             RESTARTS        AGE
hostgroup-default-58cdd4c5d6-2grr5           1/1     Running            0               8m32s
hostgroup-private-ingress-6cc48f6fb8-lrqr4   1/1     Running            0               8m32s
hostgroup-public-ingress-5fd5f89777-7nrwg    1/1     Running            0               8m32s
nats-54d58c64c4-p6bk4                        1/1     Running            0               8m32s
runtime-operator-7fb4c446d4-5s487            0/1     CrashLoopBackOff   6 (2m22s ago)   8m32s

Logs:

kubectl logs -f runtime-operator-7fb4c446d4-5s487 -n wasmcloud-system
exec /usr/local/bin/runtime-operator: exec format error

Describe:

kubectl describe pod runtime-operator-7fb4c446d4-5s487 -n wasmcloud-system
Name:             runtime-operator-7fb4c446d4-5s487
Namespace:        wasmcloud-system
Priority:         0
Service Account:  operator-dev-runtime-operator
Node:             wasmcloud-control-plane/172.18.0.2
Start Time:       Mon, 17 Nov 2025 13:46:22 +0300
Labels:           app.kubernetes.io/instance=operator-dev
                  app.kubernetes.io/managed-by=Helm
                  app.kubernetes.io/name=runtime-operator
                  app.kubernetes.io/version=0.1.0
                  helm.sh/chart=runtime-operator-0.1.0
                  pod-template-hash=7fb4c446d4
                  wasmcloud.com/name=runtime-operator
Annotations:      <none>
Status:           Running
IP:               10.244.0.9
IPs:
  IP:           10.244.0.9
Controlled By:  ReplicaSet/runtime-operator-7fb4c446d4
Containers:
  runtime-operator:
    Container ID:  containerd://c986650d35830fb3f62bd16fcb852fa26dc79366326ff3ae74dc9c575ba9065a
    Image:         ghcr.io/wasmcloud/runtime-operator:0.1.0
    Image ID:      ghcr.io/wasmcloud/runtime-operator@sha256:6cf0520d75aac6ccc68822cf53520adfafe14cb8100463e0f8708fc4b20a514c
    Port:          <none>
    Host Port:     <none>
    Args:
      -nats-url=nats://nats:4222
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    255
      Started:      Mon, 17 Nov 2025 13:52:32 +0300
      Finished:     Mon, 17 Nov 2025 13:52:32 +0300
    Ready:          False
    Restart Count:  6
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-qgmvj (ro)
Conditions:
  Type                        Status
  PodReadyToStartContainers   True 
  Initialized                 True 
  Ready                       False 
  ContainersReady             False 
  PodScheduled                True 
Volumes:
  kube-api-access-qgmvj:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    Optional:                false
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  11m                  default-scheduler  Successfully assigned wasmcloud-system/runtime-operator-7fb4c446d4-5s487 to wasmcloud-control-plane
  Normal   Pulled     10m                  kubelet            Successfully pulled image "ghcr.io/wasmcloud/runtime-operator:0.1.0" in 2.877s (27.852s including waiting). Image size: 31947066 bytes.
  Normal   Pulled     10m                  kubelet            Successfully pulled image "ghcr.io/wasmcloud/runtime-operator:0.1.0" in 559ms (559ms including waiting). Image size: 31947066 bytes.
  Normal   Pulled     10m                  kubelet            Successfully pulled image "ghcr.io/wasmcloud/runtime-operator:0.1.0" in 629ms (629ms including waiting). Image size: 31947066 bytes.
  Normal   Pulled     9m54s                kubelet            Successfully pulled image "ghcr.io/wasmcloud/runtime-operator:0.1.0" in 601ms (601ms including waiting). Image size: 31947066 bytes.
  Normal   Pulled     9m10s                kubelet            Successfully pulled image "ghcr.io/wasmcloud/runtime-operator:0.1.0" in 582ms (582ms including waiting). Image size: 31947066 bytes.
  Normal   Created    7m47s (x6 over 10m)  kubelet            Created container: runtime-operator
  Normal   Started    7m47s (x6 over 10m)  kubelet            Started container runtime-operator
  Normal   Pulled     7m47s                kubelet            Successfully pulled image "ghcr.io/wasmcloud/runtime-operator:0.1.0" in 646ms (646ms including waiting). Image size: 31947066 bytes.
  Normal   Pulling    4m55s (x7 over 11m)  kubelet            Pulling image "ghcr.io/wasmcloud/runtime-operator:0.1.0"
  Normal   Pulled     4m55s                kubelet            Successfully pulled image "ghcr.io/wasmcloud/runtime-operator:0.1.0" in 611ms (611ms including waiting). Image size: 31947066 bytes.
  Warning  BackOff    26s (x49 over 10m)   kubelet            Back-off restarting failed container runtime-operator in pod runtime-operator-7fb4c446d4-5s487_wasmcloud-system(4a08bc19-e432-4c54-894c-271ef2c83a20)

[Mees-Molenaar]

Hi,

I ran into the same issue and I figured out that the runtime-operator:0.1.0 was only built for ARM.
They published 0.1.3 for the runtime-operator which was build for AMD.

https://github.com/orgs/wasmCloud/packages/container/package/runtime-operator

To use the 0.1.3 tag, I changed the charts/runtime-operator/values.yaml, but it would be better to charts/runtime-operator/charts.yaml

[if0ne]

Thanks it works