error: failed to solve: failed to push swr.test.com/test/busybox:test: unexpected status: 401 Unauthorized

I am currently unable to push images to my private image repository. My private image repository needs to be verified, but I am afraid I have configured a password

Here are my commands for building containers:

nerdctl run -d --name buildkitd --privileged -e REGISTRY_USERNAME=test -e REGISTRY_PASSWORD=test moby/buildkit:latest

Here is my command to build an image:

buildctl build --frontend dockerfile.v0 --local context=. --local dockerfile=. --output type=image,name=swr.test.com/test/busybox:test,push=true

[+] Building 3.7s (6/6) FINISHED
 => [internal] load build definition from Dockerfile                       0.0s
 => => transferring dockerfile: 66B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
 => [internal] load metadata for docker.io/library/busybox:latest          1.9s
 => [1/2] FROM docker.io/library/busybox:latest@sha256:2376a0c12759aa1214  0.0s
 => => resolve docker.io/library/busybox:latest@sha256:2376a0c12759aa1214  0.0s
 => CACHED [2/2] RUN ls /                                                  0.0s
 => ERROR exporting to image                                               1.7s
 => => exporting layers                                                    0.0s
 => => exporting manifest sha256:a355023ed637865c1a9cc4263844a035737ee859  0.0s
 => => exporting config sha256:01397f0cc5b2af4bd0ea2f5c165dbff00d1d3c572f  0.0s
 => => pushing layers                                                      1.7s
 -> exporting to image:
error: failed to solve: failed to push swr.lan.aiminjie.com/amj/busybox:test: unexpected status: 401 Unauthorized

Start by reproducing the failure with the supplied nerdctl buildkitd command and buildctl build command against the private registry. Trace the image push and authentication path from the buildctl entry point; done means identifying why the registry returns 401 and documenting or testing a confirmed fix. No source file or test is named in the issue.