nginx-container icon indicating copy to clipboard operation
nginx-container copied to clipboard

Nginx high-performance HTTP server and reverse proxy container images based on Red Hat Software Collections and intended for OpenShift and general usage. Users can choose between Red Hat Enterprise Li...

Results 26 nginx-container issues
Sort by recently updated
recently updated
newest added

This is a PoC so far, meant to be available in quay.io initially, but ready to review and merge. The change adds a new version with a focus to deliver...

READY-for-REVIEW

This pull request tests nginx-versions separately

- add -P to docker run when running container tests Publish all exposed ports to random ports on the host interface. Add function for getting actual mapped port, and do...

pr/missing-review

Trying to build 1.12 on RHEL following To build a RHEL7 based Nginx image, you need to run Docker build on a properly subscribed RHEL machine. ``` $ git clone...

I have a simple `nginx.conf` at the root of my `git` repository. I want to launch Nginx in a pod with this command: `oc new-app registry.access.redhat.com/rhscl/nginx-114-rhel7~https://github.com/user/repo.git` The build and deployment...

**Environment : Openshift 4.7.9** **Log** ```bash= oc new-app nginx:1.18~https://github.com/sclorg/nginx-container.git --context-dir=1.18/test/test-app/ error: the image match "nginx:1.18" for source repository "https://github.com/sclorg/nginx-container.git" does not appear to be a source-to-image builder. - to attempt...

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...

oc new-app nginx:1.18~https://github.com/sclorg/nginx-container.git --context-dir=1.18/test/test-app/ error: the image match "nginx:1.18" for source repository "https://github.com/sclorg/nginx-container.git" does not appear to be a source-to-image builder. - to attempt to use this image as a...

Right now the nginx.conf provided by s2i by default includes a block: ``` location { } ``` in the `default_server` block. When serving an SPA at root this causes problems....