Gitlab-ce docker with minio docker, return 411 Length Required and 204 No Content

Hey there,
I am trying to use lfs with gitlab-ce docker and minio docker in a local network only. Following instruction from this doc
I had gitlab-ce LFS project setup fine without object store, but I got error 411 all the time when I tried to git push with LFS once I start to use minio. I am not an expert, just trying to play around with my local gitlab. Does anyone know what went wrong? or can someone point me to any ref/read?

OS: CentOS 7.9.2009
gitlab-ce version: 13.7.1
minio version: 2020-12-26T01:35:54Z
Docker Version 20.10.1 build 831ebea
docker-compose Version 1.27.4 build 40524192


git push returned

error: failed to push some refs to ‘http://10.100.10.211:8087/root/lfs2.git

mc admin trace minio returned

06:42:23.231 [411 Length Required] s3.PutObject minio:9000/lfs-objects/tmp/uploads/1609224143-17507-0002-5177-0dfd006ebe591063dfda455cc073389c?AWSAccessKeyId=minio&Signature=L%2B09TCO5kRu%2FS3nAJgv%2FueJMO%2BU%3D&Expires=1609239443 172.18.0.3 8.314ms ↑ 50 B ↓ 703 B
06:42:23.241 [204 No Content] s3.DeleteObject minio:9000/lfs-objects/tmp/uploads/1609224143-17507-0002-5177-0dfd006ebe591063dfda455cc073389c?AWSAccessKeyId=minio&Signature=1DD1Zvxw2r9cqJQGTWjemUNzDN8%3D&Expires=1609239443 172.18.0.3 507µs ↑ 47 B ↓ 197 B
06:42:23.243 [204 No Content] s3.DeleteObject minio:9000/lfs-objects/tmp/uploads/1609224143-17507-0002-5177-0dfd006ebe591063dfda455cc073389c?AWSAccessKeyId=minio&Signature=1DD1Zvxw2r9cqJQGTWjemUNzDN8%3D&Expires=1609239443 172.18.0.3 490µs ↑ 47 B ↓ 197 B

gitlab.rb, I’d tried aws_signature_version 2 and 4, no difference

external_url 'http://10.100.10.211:8087'
gitlab_rails['gitlab_shell_ssh_port'] = 2287
gitlab_rails['lfs_enabled'] = true
gitlab_rails['lfs_storage_path'] = "/var/opt/gitlab/gitlab-rails/shared/lfs-objects"
gitlab_rails['lfs_object_store_enabled'] = true
gitlab_rails['lfs_object_store_direct_upload'] = true
gitlab_rails['lfs_object_store_background_upload'] = false
gitlab_rails['lfs_object_store_proxy_download'] = true
gitlab_rails['lfs_object_store_remote_directory'] = "lfs-objects"
gitlab_rails['lfs_object_store_connection'] = {
    'provider' => 'AWS',
    'region' => 'eu-west-1',
    'aws_access_key_id' => 'minio',
    'aws_secret_access_key' => 'minio123key',
    'aws_signature_version' => 2,
    'enable_signature_v4_streaming' => false,
    'endpoint' => 'http://minio:9000',
    'host' => 'minio',
    'path_style' => true
}

gitlab-ce docker-compose.yml

version: "3.8"
services:
    gitlab-ce:
        container_name: gitlab-ce
        image: gitlab/gitlab-ce:latest
        hostname: gitlabe-ce
        ports:
            - '1443:443'
            - '8087:8087'
            - '2287:2287'
        volumes:
            - /srv/gitlab-ce/config:/etc/gitlab
            - /srv/gitlab-ce/logs:/var/log/gitlab
            - /srv/gitlab-ce/data:/var/opt/gitlab
        deploy:
            resources:
                limits:
                    cpus: '1.0'
                    memory: 16G

        networks:
            - minio_gitlab-network
        restart: unless-stopped

networks:
    minio_gitlab-network:
        external: true

minio docker-compose.yml

version: "3.8"

services:
    minio:
        container_name: minio
        image: minio/minio:latest
        hostname: minio
        volumes:
            - /mnt/temp/han_ho/miniodata:/data
        environment:
            MINIO_ACCESS_KEY: minio
            MINIO_SECRET_KEY: minio123key
        ports:
            - "9000:9000"
        command: server /data
        networks:
            - gitlab-network

networks:
    gitlab-network:
        driver: bridge

Does it work if you switch to using consolidated object storage configuration?