Reputation
Badges 1
36 × Eureka!GrumpyPenguin23 thanks for clarifying 😄 I must say the message on pricing page is so confusing. But I got what you meant now 😄
"NetworkSettings": {
"Bridge": "",
"SandboxID": "xx",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {
"8008/tcp": [
{
"HostIp": "0.0.0.0",
"HostPort": "8008"
}
],
` "808...
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
do you think it happened because of container firewall?
here is my network return after docker inspect
curl inside clearml-apiserver works just fine 😄
What am I supposed to set CLEARML_HOST_IP
value?
I was running a task, then I clone it. I queued the second one and it is pending till now.
does it mean I have low mem allocated for docker container?
AgitatedDove14 GrumpyPenguin23
Ah I see! Thanks!
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?
host: "localhost:9000"
key: "minioadmin"
secret: "minioadmin"
host: "localhost:9000"key: "minioadmin"
                    secret: "minioadmin"
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...
clearml-data close --id 1134b2601acc470698232f7f6610cd9c --storage
s3://localhost:9000/minio/test
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
yeah from the host curl return curl: (56) Recv failure: Connection reset by peer.
I believe host address of apiserver is not set to 0.0.0.0
I think because clearml-apiserver is binded to 127.0.0.1 inside docker container instead of 0.0.0.0