Specify registry for nginx (#2321) #2338
Conversation
Currently no registry is set for nginx, with leads to a few issues:
* It's being pulled from docker.io and sometimes bails out due to rate
limiting.
* With podman it can cause an issue with short-name resolution:
```
short-name resolution enforced but cannot prompt without a TTY
```
Promote nginx from a non_qa to qa image.
Molter73
added
build-builder-image
rebuild-test-container
|
Why was |
|
|
erthalion
force-pushed
the
fix/nginx-release-3.20
branch
from
8cce9d6 to
0630bfe
Compare
It's a refactoring, which has nothing to do in a back-patch PR.
Theoretically yes, practically this would be visible in broken CI tests. No failures, no problem. |
As long as we end-up having the same definitions matching the same version numbers, I think it is fine. Actually, this looks like if we just had branched off master. |
Description
Currently no registry is set for nginx, with leads to a few issues:
It's being pulled from docker.io and sometimes bails out due to rate limiting.
With podman it can cause an issue with short-name resolution:
Promote nginx from a non_qa to qa image.
Checklist
Automated testing
If any of these don't apply, please comment below.