We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While using given step in doc getting mentioned error and POD status is "CrashedLoopBackOff"
When I am checking POD log I am getting below,
Log:
"This is a S2I rhel base image.
To use it in OpenShift, run:
oc new-app nginx:1.16~https://github.com/sclorg/nginx-container.git --context-dir=1.16/test/test-app/
You can then run the resulting image via:
docker run -p 8080:8080 nginx-sample-app
Alternatively, to run the image directly using podman or docker, or how to use it as a parent image in a Dockerfile, see documentation at
https://github.com/sclorg/nginx-container/blob/master/1.16/README.md."
The text was updated successfully, but these errors were encountered:
@rdkdinesh Can you please provide more traces? Did you upload nginx imagestreams into OpenShift? What kind of OpenShift do you use?
Thanks for the response.
If the issue is not valid anymore, please close it. Thanks.
Sorry, something went wrong.
No branches or pull requests
While using given step in doc getting mentioned error and POD status is "CrashedLoopBackOff"
When I am checking POD log I am getting below,
Log:
"This is a S2I rhel base image.
To use it in OpenShift, run:
oc new-app nginx:1.16~https://github.com/sclorg/nginx-container.git --context-dir=1.16/test/test-app/
You can then run the resulting image via:
docker run -p 8080:8080 nginx-sample-app
Alternatively, to run the image directly using podman or docker, or how to use it as a parent image in a Dockerfile, see documentation at
https://github.com/sclorg/nginx-container/blob/master/1.16/README.md."
The text was updated successfully, but these errors were encountered: