Using effective pull policy of [always] for container docker:latest
Using docker image sha256:b2a8bf985f76be7345c0c827c568db287ccb4dfad919a4693488224e3644fb0c for docker:latest with digest docker@sha256:c0872aae4791ff427e6eda52769afa04f17b5cf756f8267e0d52774c99d5c9de ...
$ echo docker login -u $CI_REGISTRY_USER --password-stdin $CI_REGISTRY
docker login -u tcr --password-stdin k8s-t0.tencentcloudcr.com
$ docker login -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD" $CI_REGISTRY
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Get "https://k8s-t0.tencentcloudcr.com/v2/": unauthorized: 
section_end:1755160147:step_script
section_start:1755160147:cleanup_file_variables
Cleaning up project directory and file based variables
section_end:1755160147:cleanup_file_variables
ERROR: Job failed: exit code 1