Hi everyone. I have a question about kubectl run command. Problem: declaritive w . . .

Kubernetes-Slack Discussions
#1

Hye Jin Park:
Hi everyone. I have a question about kubectl run command.
Problem: declaritive way works fine. but Imperative way doesn’t work… :confused:

  1. This works fine.
apiVersion: v1
kind: Pod
metadata:
  labels:
    run: test
  name: test
spec:
  containers:
  - args: ["/bin/sh","-c","--","while true; do sleep 60; done;"]
    image: busybox
    name: test
    resources: {}
  dnsPolicy: ClusterFirst
  restartPolicy: Always
status: {}

$ kubectl apply -f test.yaml

  1. This doesn’t work.
kubectl run test --image=busybox -- /bin/bash -c -- while true; do sleep 10; done;
> bash: syntax error near unexpected token 'do'

kubectl run test --image=busybox -- /bin/bash -c -- 'while true; do sleep 10; done;'
> Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown
#2

Paweł Cyrklaf:
I can create without any problem

image.png
image.png1145×403 27.7 KB

#3

Hye Jin Park:
@Paweł Cyrklaf Thank you for replying!
I found the command was

kubectl run test --image=busybox -- /bin/bash -c -- while true; do sleep 10; done;

except --dry-run and -o option. sorry ;;

#4

Hye Jin Park:
I also rewrote the first message.

#5

Paweł Cyrklaf:
Ok so, you should add the command in an apostrophe and change /bin/bash to /bin/sh . I mean

kubectl run test --image=busybox -- /bin/sh -c  -- 'while true; do sleep 10; done;'
#6

Paweł Cyrklaf:

image.png
image.png951×178 20.4 KB

#7

Paweł Cyrklaf:
@Hye Jin Park Look at difference between declarative and imperative. In declarative you use /bin/sh, but in imperative you use /bin/bash :slight_smile:

#8

Hye Jin Park:
oh!

#9

Hye Jin Park:
:anguished:

#10

Hye Jin Park:
thank you @Paweł Cyrklaf!!!

#11

Paweł Cyrklaf:
You’re welcome :slight_smile: