The pod restarting has nothing to do with the service. You could
even access the pod without defining any service using "oc rsh" or
Check the pod logs using "oc logs <pod-name>" to see if
there is an error message.
Probably you choose an image that was not intended to be run as
is, but only to be a base image for other container images. If the
image does not start a long-running process the container will
stop right after starting successfully but OSE will keep
restarting it, because OSE assumes all pods you create are
s, Fernando Lozano
How do I have to create a container with an Ubuntu
Image on OpenShift?
I made a new project:
oc new-project ubuntu
oc new-app ubuntu (will do an implicit pull of the right image)
A service will not be generated for DeploymentConfig "ubuntu"
because no exposed ports were detected. Use 'oc expose dc
"ubuntu" --port=[port]' to create a service.
Run 'oc status' to view your app.
So I did oc expose dc "ubuntu" --port=OpenTCPPort
Now I've service with a pod which is restarting the whole time:
already present on machine (40 times in the last 6 minutes, 30
It keeps restarting the container. Are there some parameters
you have to describe? I can't find information about it.
users mailing list
users lists openshift redhat com