Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hey, So We Noticed The

Hey, so we noticed the /var/lib/docker/overlay2 directory on the clearml-server is growing a lot in size, we added more disk space but we want to put something in place to stop this growing too much.
These are the options I’ve looked into:

  1. docker system prune - removes all stopped containers, all networks not used by at least one container, all dangling images, all dangling build cache, Problem: we don’t really know what this is pruning
  2. docker image prune --all - removes all images without at least one container associated to them
  3. Set the max-size in docker-compose.yaml for logging

Are the first 2 options safe to run without killing the server? I’m not happy on removing files without knowing what they are.
Are there any plans to automate this in the future?

  
  
Posted 3 years ago
Votes Newest

Answers 43


back up and running again, thanks for your help

  
  
Posted 3 years ago

It looks like not all the containers are up... Try sudo docker ps and see if the apiserver container is restarting...

  
  
Posted 3 years ago

not entirely sure on this as we used the custom AMI solution, is there any documentation on it?

  
  
Posted 3 years ago

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.

  
  
Posted 3 years ago

so am I right in thinking it's just the mount points that are missing?based on the output of df above

  
  
Posted 3 years ago

it looks like clearml-apiserver and clearml-fileserver are continually restarting

  
  
Posted 3 years ago

I believe you can set it on a 'per container' way as well.

  
  
Posted 3 years ago

thanks Stef, with max-size do you set it for every running service separately, or can you set it once?

  
  
Posted 3 years ago

yeah, that's usually the case when you get an empty dashboard

  
  
Posted 3 years ago

Check sudo docker logs <container-name>

  
  
Posted 3 years ago

no, they are still rebooting. i've looked in /opt/clearml/logs/apiserver.log no errors

  
  
Posted 3 years ago

also, is there a list anywhere with the mount points that are needed?

  
  
Posted 3 years ago

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

  
  
Posted 3 years ago