I have a docker compose with diferent services.

  # Minio storage service
  findra-minio:
    container_name: findra-minio
    image: minio/minio
    command: server /data --console-address ":${FORWARD_MINIO_CONSOLE_PORT:-9002}" --address ":${FORWARD_MINIO_PORT:-9001}"
    ports:
      - '${FORWARD_MINIO_PORT:-9001}:9001'
      - '${FORWARD_MINIO_API_PORT:-9002}:9002'
    environment:
      MINIO_ROOT_USER: ${MINIO_ROOT_USER}
      MINIO_ROOT_PASSWORD: ${MINIO_ROOT_PASSWORD}
    healthcheck:
      test: ["CMD", "curl -k -f http://127.0.0.1:9001/minio/health/live || exit 1"]
      interval: 30s
      timeout: 10s
      retries: 5
    volumes:
      - type: volume
        source: findra_minio
        target: /data
    networks:
      - backend

  # Redis database for caching
  findra-redis:
    image: redis:7-alpine
    container_name: findra-redis
    restart: unless-stopped
    volumes:
      - type: volume
        source: findra_redis
        target: /data
    healthcheck:
      test: ["CMD", "redis-cli", "ping"]
      interval: 30s
      timeout: 10s
      retries: 5
    networks:
      - backend

and the MinIO container is unhealthy, and even when I run curl -I http://127.0.0.1:9001/minio/health/live , it returns a status 200.

HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Length: 0
Server: MinIO
Strict-Transport-Security: max-age=31536000; includeSubDomains
Vary: Origin
X-Amz-Id-2: 7987905dee74cdeb212432486a178e511309594cee7cb75f892cd53e35f09ea4
X-Amz-Request-Id: 17E63796A4A97415
X-Content-Type-Options: nosniff
X-Xss-Protection: 1; mode=block
Date: Sun, 28 Jul 2024 00:03:47 GMT

If I do docker ps we can see:

The difference I can see is that the command in MinIO is different from the others.