Reputation
Badges 1
26 × Eureka!Okay, backup in progress
Okay, I think I get what you're saying. How can I set up a clearml-agent with access-all creds with custom entries?
We would prefer for it to be per Task secret so team members can use their creds and passwords
Yes, I just define the env variables when using clearml-task instead of defining them in conf file
Reports are working after restoring the data from backup! Thank you.
This is the server version:WebApp: 1.5.0-186 • Server: 1.5.0-186 • API: 2.18
This is version of clearml-task:ClearML launch - launch any codebase on remote machine running clearml-agent Version 1.1.6
Hi David, I will open an issue. Do you have an estimate when this could be fixed?
I reported the issue: https://github.com/allegroai/clearml-server/issues/146
About the tasks that disappeared: you do not see these tasks at all or you see these tasks with no results?
I don't see these tasks at all
I do have backup of data. What's the exact process of rolling back?
I didn't see that, I didn't run it
Okay, I have a backup of all data before the update.
I can try restoring the database from the backup on v1.9.0.
Regarding the github issue - Can you send the docker-compose you used for 1.9 that works and 1.10 that doesn't work for you?
The docker-compose.yml
file is exactly the same with the difference of changing the latest
tag to 1.9.0
AgitatedDove14 Maybe I'm missing something, but clearml-task
has --docker_args
argument which enables passing any env variable to the docker container that will be running the code.
My idea is that each team member adds their creds to --docker_args
which would pass it to the docker container and the creds would be available for the task.
It seems to me that the only problem in passing credentials via --docker_args
is that are currently shown in the plain form in th...
Is there a way to receive updates when new version of ClearML is out?
version: "3.6"
services:
apiserver:
command:
- apiserver
container_name: clearml-apiserver
image: allegroai/clearml:1.9
restart: unless-stopped
volumes:
- /opt/clearml/logs:/var/log/clearml
- /opt/clearml/config:/opt/clearml/config
- /opt/clearml/data/fileserver:/mnt/fileserver
depends_on:
- redis
- mongo
- elasticsearch
- fileserver
environment:
CLEARML_ELASTIC_SERVICE_HOST: elasticsearch
CLEARML_ELASTIC...
What's weird to me is that only part of the data has been migrated, and the other part is not available after update
Had to learn that the hard way, obviously 😄
Hmm, I might have messed something up. It seems that the backup has been done after the update, and not before. If I don't want to mess something up, what are my alternative options?
Hmm, I'm not sure which version the server was prior to upgrade. Old version had http://docker.elastic.co/elasticsearch/elasticsearch:7.6.2 and mongo:3.6.5
Okay, I think everything is OK now!
Thank you very much for your help. I'll make sure that backup is performed on regular basis.
Should I try to do it now?
Is there a way to reindex data in Elastic?
How do I remove the current version?
Backup is done