You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fresh installation of core on IBM kubernetes. I tried on 2 different clusters ver 1.13.10_1534 and 1.14.6_1531. Result is same:
Error: failed to create containerd task: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: "sh": executable file not found in $PATH": unknown
kubectl -n stellar-testnet get pods
NAME READY STATUS RESTARTS AGE
stellar-core-dcfccfd9b-bbf5j 0/1 CrashLoopBackOff 7 25m
stellar-core-postgresql-0 0/1 Init:CrashLoopBackOff 7 24m
Looking at the pod details, there are these commands specified:
The first command is sh
In the pod/deployment yaml, this command should to be qualified to include the path eg. /bin/sh instead of just sh
IBM support said that the issue happens is due to a containerd issue: containerd/containerd#3597
IKS will pick up the containerd fix for this when they release version 1.2.9.
Not sure (i'm new in kubernetes) but I think that sh is defined in
stellar-helm-charts/stellar-core/requirements.yaml which installing postgresql
Any idea how to solve it?
The text was updated successfully, but these errors were encountered:
Fresh installation of core on IBM kubernetes. I tried on 2 different clusters ver 1.13.10_1534 and 1.14.6_1531. Result is same:
Error: failed to create containerd task: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: "sh": executable file not found in $PATH": unknown
kubectl -n stellar-testnet get pods
NAME READY STATUS RESTARTS AGE
stellar-core-dcfccfd9b-bbf5j 0/1 CrashLoopBackOff 7 25m
stellar-core-postgresql-0 0/1 Init:CrashLoopBackOff 7 24m
Looking at the pod details, there are these commands specified:
Command:
sh
-c
mkdir -p /bitnami/postgresql/data
chmod 700 /bitnami/postgresql/data
find /bitnami/postgresql -mindepth 1 -maxdepth 1 -not -name ".snapshot" -not -name "lost+found" |
xargs chown -R 1001:1001
The first command is
sh
In the pod/deployment yaml, this command should to be qualified to include the path eg.
/bin/sh
instead of justsh
IBM support said that the issue happens is due to a containerd issue:
containerd/containerd#3597
IKS will pick up the containerd fix for this when they release version 1.2.9.
Not sure (i'm new in kubernetes) but I think that
sh
is defined instellar-helm-charts/stellar-core/requirements.yaml which installing postgresql
Any idea how to solve it?
The text was updated successfully, but these errors were encountered: