-
Notifications
You must be signed in to change notification settings - Fork 24
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
What did you do?
I attempted to push a Docker image to a Scaleway Container Registry using the serverless deploy command with the following options:
serverless deploy --debug "*" --verboseThe build process completed successfully, but the push failed with an access denied error.
What did you expect to see?
- The Docker image should be successfully pushed to the Scaleway Container Registry (
rg.fr-par.scw.cloud/redacted/redacted:latest). - No authentication or permission errors during the push process.
What did you see instead?
The build succeeded, but the push failed with the following error:
{"errorDetail":{"message":"denied: requested access to the resource is denied"},"error":"denied: requested access to the resource is denied"}Full logs:
{"stream":"Successfully built 93f0442f11c4\n"}
{"stream":"Successfully tagged rg.fr-par.scw.cloud/redacted/redacted:latest\n"}
{"status":"The push refers to repository [rg.fr-par.scw.cloud/redacted/redacted]"}
{"status":"Preparing","progressDetail":{},"id":"35986a2b519e"}
{"status":"Preparing","progressDetail":{},"id":"8d0ae6f9d228"}
{"status":"Preparing","progressDetail":{},"id":"e5a603c4ced4"}
{"status":"Preparing","progressDetail":{},"id":"14c17f327a48"}
{"status":"Preparing","progressDetail":{},"id":"8765e43343af"}
{"status":"Preparing","progressDetail":{},"id":"a089a749d402"}
{"status":"Preparing","progressDetail":{},"id":"793ce030f540"}
{"status":"Preparing","progressDetail":{},"id":"761237d28cf3"}
{"status":"Preparing","progressDetail":{},"id":"223a9dfbfc84"}
{"status":"Preparing","progressDetail":{},"id":"e1fe230a8a53"}
{"status":"Preparing","progressDetail":{},"id":"c14d7cb786e0"}
{"status":"Waiting","progressDetail":{},"id":"793ce030f540"}
{"status":"Waiting","progressDetail":{},"id":"761237d28cf3"}
{"status":"Waiting","progressDetail":{},"id":"c14d7cb786e0"}
{"status":"Waiting","progressDetail":{},"id":"223a9dfbfc84"}
{"status":"Waiting","progressDetail":{},"id":"e1fe230a8a53"}
{"status":"Waiting","progressDetail":{},"id":"a089a749d402"}
{"errorDetail":{"message":"denied: requested access to the resource is denied"},"error":"denied: requested access to the resource is denied"}What version of Node are you using (node --version)?
$ node --version
v24.x.xDoes this issue reproduce with the latest release?
- Yes, the issue persists with the latest versions of the following packages:
"osls": "^3.58.0""serverless-scaleway-functions": "^0.4.16"
I tried to authenticate to the registry before executing the command, but the error persists but I still can push it manually.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working