Closed
Description
Hi,
My docker-compose.yml looks something like -
version: "2"
services:
client:
image: registry.centos.org/centos/centos:7
stdin_open: true
tty: true
kompose up
gives me -
WARN[0000] Unsupported stdin_open key - ignoring
WARN[0000] Unsupported tty key - ignoring
WARN[0000] [client] Service cannot be created because of missing port.
We are going to create Kubernetes Deployments, Services and PersistentVolumeClaims for your Dockerized application.
If you need different kind of resources, use the 'kompose convert' and 'kubectl create -f' commands instead.
INFO[0000] Successfully created Deployment: client
Your application has been deployed to Kubernetes. You can run 'kubectl get deployment,svc,pods,pvc' for details.
Since these keys are unsupported, the pod goes from Running to Completed to CrashLoopBackOff
$ kubectl get pods -w
NAME READY STATUS RESTARTS AGE
client-2474090665-o7wdc 0/1 ContainerCreating 0 1s
NAME READY STATUS RESTARTS AGE
client-2474090665-o7wdc 0/1 Completed 0 1s
client-2474090665-o7wdc 0/1 Completed 1 2s
client-2474090665-o7wdc 0/1 CrashLoopBackOff 1 3s
client-2474090665-o7wdc 0/1 Completed 2 16s
It would be great if stdin_open
and tty
could be supported.
Here is the equivalent in Kubernetes world -
apiVersion: extensions/v1beta1
kind: Deployment
...
spec:
...
template:
metadata:
...
spec:
containers:
- stdin: true
tty: true
image: registry.centos.org/centos/centos:7
Metadata
Assignees
Labels
No labels