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
Therefore I'M Not About To Do Clearml-Init Verification.

therefore i'm not about to do clearml-init verification. 😒

  
  
Posted 2 years ago
Votes Newest

Answers 30


since this is an enterprise machine, and you don't have sudo/root, I am wondering if there is already other docker networks/composer setups running/in use

  
  
Posted 2 years ago

HugePelican43 did you try docker ps and see that the clearml-apiserver container is up? if so, can you docker exec -it cleaml-apiserver /bin/bash and try to do the curl http://localhost:8008 from inside it?

  
  
Posted 2 years ago

oh it's not a problem.. if you can fling up the logs of ES after startup that's probably the next step.. along with a 'docker network list' output πŸ‘

  
  
Posted 2 years ago

so I am not entirely sure what else you have changed Sir

  
  
Posted 2 years ago

curl inside clearml-apiserver works just fine πŸ˜„

  
  
Posted 2 years ago

I will get back to you tmr πŸ˜„ cheers

  
  
Posted 2 years ago

thank you so much for your effort

  
  
Posted 2 years ago

πŸ‘

  
  
Posted 2 years ago

curl inside clearml-apiserver works just fineΒ 

And from outside the docker, on the machine running the docker, it fails? That's very strange...

  
  
Posted 2 years ago

I think because clearml-apiserver is binded to 127.0.0.1 inside docker container instead of 0.0.0.0

  
  
Posted 2 years ago

yeah from the host curl return curl: (56) Recv failure: Connection reset by peer.

  
  
Posted 2 years ago

I believe host address of apiserver is not set to 0.0.0.0

  
  
Posted 2 years ago

You mean for the agent-services?

  
  
Posted 2 years ago

SuccessfulKoala55

  
  
Posted 2 years ago

do you think it happened because of container firewall?

  
  
Posted 2 years ago

humhh I will ask the server admin

  
  
Posted 2 years ago

Possibly...

  
  
Posted 2 years ago

"NetworkSettings": {
"Bridge": "",
"SandboxID": "xx",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {
"8008/tcp": [
{
"HostIp": "0.0.0.0",
"HostPort": "8008"
}
],
"8080/tcp": null,
"8081/tcp": null
},
"SandboxKey": "/var/run/docker/netns/xx",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "",
"Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"MacAddress": "",
"Networks": {
"mlops_backend": {
"IPAMConfig": null,
"Links": null,
"Aliases": [
"apiserver",
"f86e5d0835f4"
],
"NetworkID": "xx",
"EndpointID": "xx",
"Gateway": "172.25.0.1",
"IPAddress": "172.25.0.6",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "xx",
"DriverOpts": null
},
"mlops_frontend": {
"IPAMConfig": null,
"Links": null,
"Aliases": [
"apiserver",
"f86e5d0835f4"
],
"NetworkID": "xx",
"EndpointID": "xx",
"Gateway": "172.26.0.1",
"IPAddress": "172.26.0.3",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "xxx",
"DriverOpts": null
}
}
}
}
]

  
  
Posted 2 years ago

I also run netstat inside the container:
netstat -an | grep LISTEN | grep 8008
tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN

  
  
Posted 2 years ago

here is my network return after docker inspect

  
  
Posted 2 years ago

What am I supposed to set CLEARML_HOST_IP value?

  
  
Posted 2 years ago

SuccessfulKoala55

  
  
Posted 2 years ago

I assign 0.0.0.0

  
  
Posted 2 years ago

BTW, from the netstat output you sent it seems like the apiserver is binded correctly inside the docker

  
  
Posted 2 years ago

Seems to be some system/docker configuration issue - maybe related to you now having admin permissions?

  
  
Posted 2 years ago

Actually, it uses the apiserver.listen.ip configuration value (which is 0.0.0.0 by default)

  
  
Posted 2 years ago

You can look at the entrypoint inside the docker (it's called wrapper.sh )

  
  
Posted 2 years ago

😒 ah it's strange. I tried all the solutions I came up with

  
  
Posted 2 years ago

but the code binds it to 0.0.0.0 by default...

  
  
Posted 2 years ago

cannot fix it

  
  
Posted 2 years ago
542 Views
30 Answers
2 years ago
one year ago
Tags