[CRASH] Ubuntu Server not supported - valkey-init crash

[PheonBest]

Crash report

Hello It seems like Valkey cannot be installed on Ubuntu Server (Ubuntu 24.04.2 LTS)

The valkey-init container fails to run:

/scripts/init.sh: 2: set: Illegal option -o pipefail

I tried to override it with my own initContainer but it's not possible.

Valkey pod logs:

Name:             n8n-valkey-74cc5f9f9b-h6v4d
Namespace:        n8n
Priority:         0
Service Account:  n8n-valkey
Node:             intelnucx/192.168.1.61
Start Time:       Fri, 14 Nov 2025 12:42:36 +0100
Labels:           app.kubernetes.io/instance=n8n-valkey
                  app.kubernetes.io/name=valkey
                  checksum/initconfig=5ac326b1344756c548fd078fc2356662
                  pod-template-hash=74cc5f9f9b
Annotations:      <none>
Status:           Pending
IP:               10.42.0.180
IPs:
  IP:           10.42.0.180
Controlled By:  ReplicaSet/n8n-valkey-74cc5f9f9b
Init Containers:
  valkey-init:
    Container ID:  containerd://4c9c3d4d06905370408ee7b18ebfadc605ed0767e486f691796e6ea375665f79
    Image:         docker.io/valkey/valkey:8.0.1
    Image ID:      docker.io/valkey/valkey@sha256:c5d4f082b76d433a38274ebb38a43cff19829a062928bdcc45611135ef54e608
    Port:          <none>
    Host Port:     <none>
    Command:
      /scripts/init.sh
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    2
      Started:      Fri, 14 Nov 2025 12:47:02 +0100
      Finished:     Fri, 14 Nov 2025 12:47:02 +0100
    Ready:          False
    Restart Count:  5
    Environment:    <none>
    Mounts:
      /data from valkey-data (rw)
      /scripts from scripts (rw)
Containers:
  n8n-valkey:
    Container ID:
    Image:         docker.io/valkey/valkey:8.0.1
    Image ID:
    Port:          6379/TCP (tcp)
    Host Port:     0/TCP (tcp)
    Command:
      valkey-server
    Args:
      /data/conf/valkey.conf
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     200m
      memory:  256Mi
    Requests:
      cpu:     50m
      memory:  128Mi
    Liveness:  exec [sh -c valkey-cli ping] delay=0s timeout=1s period=10s #success=1 #failure=3
    Startup:   exec [sh -c valkey-cli ping] delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:
      VALKEY_LOGLEVEL:  notice
    Mounts:
      /data from valkey-data (rw)
Conditions:
  Type                        Status
  PodReadyToStartContainers   True
  Initialized                 False
  Ready                       False
  ContainersReady             False
  PodScheduled                True
Volumes:
  scripts:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      n8n-valkey-init-scripts
    Optional:  false
  valkey-data:
    Type:        PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:   n8n-valkey-pvc
    ReadOnly:    false
QoS Class:       Burstable
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  5m59s                   default-scheduler  Successfully assigned n8n/n8n-valkey-74cc5f9f9b-h6v4d to intelnucx
  Normal   Pulled     2m58s (x5 over 4m21s)   kubelet            Container image "docker.io/valkey/valkey:8.0.1" already present on machine
  Normal   Created    2m57s (x5 over 4m20s)   kubelet            Created container valkey-init
  Normal   Started    2m57s (x5 over 4m20s)   kubelet            Started container valkey-init
  Warning  BackOff    2m16s (x10 over 4m19s)  kubelet            Back-off restarting failed container valkey-init in pod n8n-valkey-74cc5f9f9b-h6v4d_n8n(cfb37de8-b3e5-404c-a7f4-5fc166f4e7ca)

Installation method: Helm Values.yml:

fullnameOverride: "n8n-valkey"

image:
  repository: docker.io/valkey/valkey
  pullPolicy: IfNotPresent
  tag: "8.0.1"

dataStorage:
  enabled: true
  persistentVolumeClaimName: "n8n-valkey-pvc"
  volumeName: "valkey-data"
  accessModes:
    - ReadWriteOnce

resources:
  limits:
    cpu: 200m
    memory: 256Mi
  requests:
    cpu: 50m
    memory: 128Mi

Thank you

Additional information