
Reputation
Badges 1
36 × Eureka!here is my network return after docker inspect
I have a single gpu to serve as an agent. Currently running a task on that gpu. Can I run another task on that same GPU?
"NetworkSettings": {
"Bridge": "",
"SandboxID": "xx",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {
"8008/tcp": [
{
"HostIp": "0.0.0.0",
"HostPort": "8008"
}
],
` "808...
clearml-data close --id 1134b2601acc470698232f7f6610cd9c --storage
s3://localhost:9000/minio/testclearml-data - Dataset Management & Versioning CLI
Finalizing dataset id 1134b2601acc470698232f7f6610cd9c
Pending uploads, starting dataset upload to
s3://localhost:9000/minio/test2021-05-14 00:33:57,017 - clearml.storage - ERROR - Failed uploading: SSL validation failed for
https://localhost:9000/minio/test/.clearml.test ` [SSL: WRONG_VERSION_NUMBER] wrong versio...
curl inside clearml-apiserver works just fine 😄
host: "localhost:9000"
key: "minioadmin"
secret: "minioadmin"
GrumpyPenguin23 I'm not clear yet 😄
I deployed a self-hosted server and still not able to see it.
is that incoming feature or do I need to do anything to involve "Feature store" feature?
GrumpyPenguin23 thanks for clarifying 😄 I must say the message on pricing page is so confusing. But I got what you meant now 😄
host: "localhost:9000"key: "minioadmin"
                    secret: "minioadmin"
What am I supposed to set CLEARML_HOST_IP
value?
I think because clearml-apiserver is binded to 127.0.0.1 inside docker container instead of 0.0.0.0
humhhh idk SuccessfulKoala55 I just give this to the terminal
I think I am facing the same issue. I posted question in an earlier thread
I think you could use Clone task
AgitatedDove14 GrumpyPenguin23
Thank mate.
I realize it is available on self-deployed version of Server. I was struggling deploy it on my server, with corporate proxy things, before end-up using online server (for now).
I will try to deploy a local server again then using this feature.
cheers
😢 ah it's strange. I tried all the solutions I came up with
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