You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Dockerfile.latest-njs file contains an incorrect URL in the FROM statement.
Dockerfile.latest-njs:4 | >>> FROM nginx-s3-gateway
ERROR: failed to solve: nginx-s3-gateway: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Hello, thank you for pointing out this issue. This is actually a side effect of the fact that the test suite is coupled with the build process but you're correct that it's confusing.
Right now, I'm working on refactoring the integration test suite to be a little more manageable which will include:
Producing arm64 builds of all the images (addressing Arm64 build #196)
Separating the build and test actions while maintaining integration tests run against the artifacts to be published
The latest-njs assumes that you've locally built the mainline image. See here:
So in addition to your stated workaround of supplying the full path to the hosted image, you can also first built that image locally under that name as our build step currently does:
The Dockerfile.latest-njs file contains an incorrect URL in the FROM statement.
Dockerfile.latest-njs:4 | >>> FROM nginx-s3-gateway
ERROR: failed to solve: nginx-s3-gateway: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
To Reproduce
Environment
commit 231fa7d (HEAD -> master, origin/master, origin/HEAD)
Additional context
The issue can be resolved by updating the URL in the FROM block from nginx-s3-gateway to nginxinc/nginx-s3-gateway.
The text was updated successfully, but these errors were encountered: