upload error with minio s3

[philippkayser]

I try to upload a file with connected minio s3 bucket.

The file is visible in the bucket but the UI shows the following error. If you try it again with the same file it works fine.

"Upload failed: Failed API request: failed to tag object"

docker-compose.yml following:

version: "3.3"
services:
  gose:
    image: ghcr.io/stv0g/gose:v0.4.0
    build:
      context: .
    expose:
     - "8080"
    environment:
      GOSE_LISTEN: ":8080"
      GOSE_BASE_URL: "https://dropme.domain"
      GOSE_BUCKET: "dropme"
      GOSE_ENDPOINT: "s3.eu-central-2.wasabisys.com"
      GOSE_REGION: "eu-central-2"
      GOSE_PATH_STYLE: "true"
      GOSE_NO_SSL: "false"
      GOSE_ACCESS_KEY: "***********" # changeme!
      GOSE_SECRET_KEY: "************" # changeme!
      GOSE_MAX_UPLOAD_SIZE: "50GB"
      GOSE_PART_SIZE: "16MB"
      GOSE_SETUP_CORS: "false"
      GOSE_SETUP_BUCKET: "false"
      GOSE_SETUP_LIFECYCLE: "false"
    networks:
      - web
    labels:
      - "traefik.docker.network=web"
      - "traefik.enable=true"
      - "traefik.frontend.rule=Host:dropme.domain"
      - "traefik.port=8080"

networks:
 web:
    external: true

[stv0g]

Are you sure you are running Minio?

GOSE_ENDPOINT: "s3.eu-central-2.wasabisys.com"

looks like something else..?

Gos3 requires an S3 implementation which supports object tagging.
See https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-tagging.html

[stv0g]

I did some more research in the Wasabi object storage documentation:

https://wasabi.com/wp-content/themes/wasabi/docs/API_Guide/topics/Operations_on_Objects_Not_Supported_in_Wasabi.htm

Wasabi does not have the recently announced object tagging feature implemented. This may be added in a future release.

This makes Wasabi currently incompatible with Gos3. Sorry :(

I am also thinking about moving most of the objects metadata to a dedicated object as this might help us with implementing some of the other features like usage tracking, download counters, etc..

Thanks anyway for bringing this up, as I will keep this in mind when designing the new metadata system (See #39)