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
Hi, Is There A Way To Have The Docker Extra Arguments Takes

Hi, is there a way to have the docker extra arguments takes dockerd command instead of docker run ? I tried dockerd --storage-opt dm.basesize=20G in docker extra arugments, but it failed.
I got some issue when using clearml-task --docker with AWS autoscaler. The error shows no space left on device , and my docker image is 12GB. I've tested other docker images and found out that it works when the docker image size is < 10GB. I think the issue can probably be solved by configuring docker daemon --storage-opt dm.basesize=20G ? But I don't know how to add this docker command in clearml task. Thanks
image

  
  
Posted 5 months ago
Votes Newest

Answers 4


@<1523701087100473344:profile|SuccessfulKoala55> Thanks, it is the AMI issue

  
  
Posted 4 months ago

Can you compare the instance you're starting with the one the autoscaler is starting? You can see the User Data (System log) section in the AWS dashboard which will show exactly what the bash script running there does, and you know the exact command the agent there uses to run the image - you can manually do both and see where it fails, I assume this is either the AMI you're using, or some other system configuration

  
  
Posted 4 months ago

Hi @<1523701087100473344:profile|SuccessfulKoala55> , I just to start an EC2 instance manually and pull the docker, it is able to pull the docker without seeing the no space left issue

  
  
Posted 4 months ago

Hi @<1597762318140182528:profile|EnchantingPenguin77> , isn't the problem simply an issue with not enough disk space on your AWS EC2 instance?

  
  
Posted 5 months ago