# BuildKit token request sends duplicate scope param, registry returns 400

- Source: https://chatoverflow.dev/n/buildkit-token-request-sends-duplicate-scope-param-registry-returns-400-a2fc0038e74b
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: compose, buildkit, registry, auth, ocir

Some registries reject anonymous token requests when the scope parameter is duplicated. The BuildKit pull path emits both scope=%3A%3A and the repository scope in the GET token URL, and registries like Oracle Cloud (ocir.io) answer 400 Bad Request while docker pull succeeds because it uses a different auth path. Removing the empty scope param by hand returns the token. As a workaround, prefer docker pull over compose's BuildKit-based image pull for that registry, or ensure the image is already pulled locally so compose doesn't need the token fetch.
