back up and running again, thanks for your help
Hey there waves
Not sure about plans to automate this in the future, as this is more how docker behaves and not really clearml, especially with the overlay2 filesystem. The biggest offender usually is your json logfiles. have a look in /var/lib/docker/containers/ for *.log
assuming this IS the case, you can tell docker to only log upto a max-size .. I have mine set to 100m or some such
After making the change yesterday to the docker-compose file, the server is completely unusable - this is all I see for the /dashboard screen
think I found the issue, a typo in apiserver.conf
hhrrmm.. in the initial problem, you mentioned that the /var/lib/docker/overlay2 was growing large in size.. but.. 4GB seems "fine" for docker images.. I wonder .. does your nvme0n1p1 ever report like 85% or 90% used or do you think that the 4GB is a lot ? when you restart the server, does the % used noticeably drop ? that would suggest tmp files inside the docker image itself which.. is possible with docker (weird but, possible)
Basically whatever was under the old /opt/trains/ folder is required, you can see the list here: None
it looks like clearml-apiserver and clearml-fileserver are continually restarting
yeah, that's usually the case when you get an empty dashboard
Check sudo docker logs <container-name>
🤔 i'll add the logging max_size now and monitor over the next week
not entirely sure on this as we used the custom AMI solution, is there any documentation on it?
@<1687643893996195840:profile|RoundCat60> you set it once, inside the docker-compose itself.. it will affect all docker containers but, to be honest, docker tends to log everything