Reputation
Badges 1
38 × Eureka!After making the change yesterday to the docker-compose file, the server is completely unusable - this is all I see for the /dashboard screen
incidentally we turn off the server every evening as it's not used overnight, we've not faced issues with it starting up in the morning or noticed any data loss
Is there a way you can allow our account to make a copy of the AMI and store it privately?
Hey @<1523701205467926528:profile|AgitatedDove14> I am helping Max to get this working. I ran the clearml-agent init and now have the correct entries in the clearml.conf file.
Created an ssh key from the agent, uploaded it to the git repo, but still getting this error:
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
If I manually ssh on to the agent, and run:
`git clon...
our setup currently consists of an EC2 instance for clearml-server and one for clearml-agent. We're not using a load balancer at the moment.
all sorted, I somehow missed the documentation about the mongodb migration
thanks Stef, with max-size do you set it for every running service separately, or can you set it once?
not entirely sure on this as we used the custom AMI solution, is there any documentation on it?
yep, in most of them:
/opt/clearml/config
apiserver.conf
clearml.conf
/opt/clearml/data/elastic_7
/nodes
/opt/clearml/data/fileserver
<empty>
/opt/clearml/data/mongo/configdb
<empty>
/opt/clearml/data/mongo/db
collection/index files, /diagnostic.data, /journal etc
/opt/clearml/data/redis
dump.rdb
/opt/clearml/logs
apiserver.log.x, filserver.log (0 bytes)
Is it possible to use an IAM role rather than user credentials in the clearml.conf file?
Hi @<1523701205467926528:profile|AgitatedDove14>
Yes the clearml-server AMI - we want to be able to back it up and encrypt it on our account
Morning, we got to 100% used which is what triggered this investigation. When we initially looked at overlay2 it was using 8GB, so now seems to be acceptable.
I added this to each of the containers
logging:
options:
max-file: 5
max-size: 10m