@<1585078752969232384:profile|FantasticDuck7> best thing would be to put that in the /opt/clearml/config free which is already mapped into the server configuration. Easiest would be to put that in a services.conf file and add a top key there named storage_credentials under which you can put the same configuration

@<1585078752969232384:profile|FantasticDuck7> The best would be to copy this file to the host, edit it and map this file into the container instead of the original one. The single file mapping in the docker-compose file should look like this:

    volumes:
      - type: bind
        source: <the path to the config file on the host>
        target: /opt/clearml/apiserver/config/default/services/storage_credentials.conf

You should do it for the async_delete service. Not for the apiserver

@<1523701087100473344:profile|SuccessfulKoala55> Thank you! I think I've done something wrong (It doesn't delete now). Correct me please

• I've created file on clearml host machine /opt/clearml/config/services.conf with content as in the pic
• Restarted container with docker restart async-delete
  

@<1523701994743664640:profile|AppetizingMouse58> @<1523701087100473344:profile|SuccessfulKoala55> It worked as intended! Thank you once again :hugging_face:

@<1523701994743664640:profile|AppetizingMouse58> Hi! Thank you for a quick response! Should I edit the configuration file directly in apiserver container like in screenshot? Is there a better, more consistent way to do that (I don't want to edit this config again if I recreate container for some reason) ?

Ok, so there is no mapping for the whole config folder or specific config file that you changed. That's why async_delete does not get your updated configuration. You can do one of the following: either add here mapping for the specific file like you did earlier or map the whole config folder like apiserver service does:

• /opt/clearml/config:/opt/clearml/config
  The second way is probably more flexible

@<1523701994743664640:profile|AppetizingMouse58> Thanks a lot! That worked ☺

🙂

Hi @<1585078752969232384:profile|FantasticDuck7> , there is an apiserver configuration file apiserver->config->default->services->storage_credentials.conf
It contains the parameters for accessing files on the external storages like s3, google or azure. Please provide the same minio server access parameters as you do for the SDK configuration.
The actual deletion is performed by the async_delete service. You can inspect its logs with "sudo docker logs async_delete" command. Before configuring the access params it is likely that you will see the errors in the logs about missing s3 credentials. After configuring the logs and restarting the server you should see successful deletions of the requested files. It will not handle the files that failed prior to the change but the new deletions should work

@<1585078752969232384:profile|FantasticDuck7> What volume mappings do you have for the async_delete service in the docker-compose.yaml file?

@<1523701994743664640:profile|AppetizingMouse58>

Hello @<1585078752969232384:profile|FantasticDuck7> , can you explain step by step for minio setup. I tried that too, but i got error when uploading object like in this thread: None .

Hi! Try excluding “http/https” from the uri in the config. Have you configured your client correctly?Try adding “output_uri” (or smth like that) when initializing your Task.