MINIO registry | docker | aws.Config.CredentialsChainVerboseErrors

Hello,

Im trying to deploy gitlab as docker with minio for storage (registry first .).

      GITLAB_OMNIBUS_CONFIG: |
        external_url 'https://gitlab.com.ltd:8443'
        registry_external_url 'https://registry.com.ltd:5005'
        registry_nginx['listen_port'] = 5005
        gitlab_sshd['enable'] = false
        nginx['redirect_http_to_https'] = true
        registry['log_level'] = 'debug'
        registry['enable'] = true
        registry['storage'] = {
          's3' => {
            'provider' => 'AWS',
            'region' => 'eu-west-3',
            'aws_access_key_id' => 'bW6enEOUDsEXQGF8eMUV',
            'aws_secret_access_key' => 'S8yIvpKwv01FA57cHdc1f71bGRmoe1vi8tSkLcdH',
            'regionendpoint' => 'https://s3.com.ltd',
            'pathstyle' => true,
            'bucket' => 'gitlab-registry',
            'v4Auth' => true,
            'loglevel' =>  'logdebug',
          }
        }

Please explain me what is misconfigured here because based on the few info that you provide in your documentation, this should be enough.

I dont have DNS issue, TLS certificates are wildcard and working, I can curl or even use the s3 api to interact with minio using the API key provided above :

~/devops$ docker run --network cicd_local_cicd --rm -ti -v ~/.aws:/root/.aws amazon/aws-cli --endpoint-url https://s3.com.ltd:9000 s3 ls
2024-03-18 09:20:47 gitlab-artifacts
2024-03-18 09:21:33 gitlab-dependency-proxy
2024-03-18 09:21:13 gitlab-lfs
2024-03-18 09:21:01 gitlab-mr-diffs
2024-03-18 09:21:27 gitlab-packages
2024-03-18 09:21:44 gitlab-pages
2024-03-18 13:51:22 gitlab-registry
2024-03-18 09:21:38 gitlab-terraform-state
2024-03-18 09:21:21 gitlab-uploads

I'm stuck with the following error despite supposly been in "debug", which basically does not say much :

gitlab_server  | 2024-03-18_15:25:12.49730 time="2024-03-18T15:25:12.497Z" level=info msg="S3: retrying after error" delay_s=3.517781357 error="NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors"
gitlab_server  | 2024-03-18_15:25:10.49614 -----------------------------------------------------
gitlab_server  | 2024-03-18_15:25:11.49673 2024/03/18 15:25:11 DEBUG: Request ec2metadata/GetMetadata Details:
gitlab_server  | 2024-03-18_15:25:11.49676 ---[ REQUEST POST-SIGN ]-----------------------------
gitlab_server  | 2024-03-18_15:25:11.49677 GET /latest/meta-data/iam/security-credentials/ HTTP/1.1
gitlab_server  | 2024-03-18_15:25:11.49677 Host: 169.254.169.254
gitlab_server  | 2024-03-18_15:25:11.49678 User-Agent: aws-sdk-go/1.46.7 (go1.21.6; linux; amd64)
gitlab_server  | 2024-03-18_15:25:11.49678 Accept-Encoding: gzip
gitlab_server  | 2024-03-18_15:25:11.49679
gitlab_server  | 2024-03-18_15:25:11.49679
gitlab_server  | 2024-03-18_15:25:11.49680 -----------------------------------------------------
gitlab_server  | 2024-03-18_15:25:16.01837 2024/03/18 15:25:16 DEBUG: Request ec2metadata/GetToken Details:
gitlab_server  | 2024-03-18_15:25:16.01841 ---[ REQUEST POST-SIGN ]-----------------------------
gitlab_server  | 2024-03-18_15:25:16.01841 PUT /latest/api/token HTTP/1.1
gitlab_server  | 2024-03-18_15:25:16.01842 Host: 169.254.169.254
gitlab_server  | 2024-03-18_15:25:16.01842 User-Agent: aws-sdk-go/1.46.7 (go1.21.6; linux; amd64)
gitlab_server  | 2024-03-18_15:25:16.01843 Content-Length: 0
gitlab_server  | 2024-03-18_15:25:16.01843 X-Aws-Ec2-Metadata-Token-Ttl-Seconds: 21600
gitlab_server  | 2024-03-18_15:25:16.01844 Accept-Encoding: gzip
gitlab_server  | 2024-03-18_15:25:16.01844
gitlab_server  | 2024-03-18_15:25:16.01845
gitlab_server  | 2024-03-18_15:25:16.01845 -----------------------------------------------------

I even try to provide the access key / secret using the env var of AWS but it does not change a thing.

Do you plan maybe to improve your documentation by providing a working example ?

Thanks

Edited by x-077