Reputation
Badges 1
186 × Eureka!any suggestions on how to fix it?
yes. we upload artifacts to Yandex.Cloud S3 using ClearML. we set " s3://storage.yandexcloud.net/clearml-models " as output uri parameter and add this section to the config:{
host: "
http://storage.yandexcloud.net "
key: "KEY"
secret:"SECRET_KEY",
secure: true
}
this works like a charm. but download button in UI is not working
we do log a lot of the different metrics, maybe this can be part of the problem
after the very first click, there is a popup with credentials request. nothing happens after that
it will probably screw up my resource monitoring plots, but well, who cares 😃
not quite. for example, I’m not sure which info is stored in Elastic and which is in MongoDB
not necessarily, there are rare cases when container keeps running after experiment is stopped or aborted
will do!
I guess I could manually explore different containers and their content 😃 as far as I remember, I had to update Elastic records when we moved to the new cloud provider in order to update model URLs
on the side note, is there any way to automatically give more meaningful names to the running docker containers?
we're using os.getenv in the script to get a value for these secrets
it works, but it's not very helpful since everybody can see a secret in logs:
Executing: ['docker', 'run', '-t', '--gpus', '"device=0"', '-e', 'DB_PASSWORD=password']
right now we can pass github secrets to the clearml agent training containers ( CLEARML_AGENT_GIT_PASS) to install private repos
we need a way to pass secrets to access our database with annotations
parents and children. maybe tags, maybe separate tab or section, idk. I wonder if anyone else is interested in this functionality, for us this is a very common case