Our core mission is driving the future of distributed cloud computing. The infrastructure of the internet is siloed and byzantine. We can do better.

GRAVITL

That and the latest version tag images are broken

which image?  netmaker, netmaker-ee, netclient, netclient-userspace?

`ubuntu@arm64:~$ sudo docker run -it --entrypoint /bin/bash gravitl/netclient:v0.16.3 
bash-5.1# ls
netclient     netclient.sh
bash-5.1# 

`

`ubuntu@arm64:~$ sudo docker run -it --entrypoint /bin/bash gravitl/netclient:latest
Unable to find image 'gravitl/netclient:latest' locally
latest: Pulling from gravitl/netclient
Digest: sha256:c716a8a3b60fd2488a741bc77dac8e4c18cd54e740dc64ac5f76bbc25a0161df
Status: Downloaded newer image for gravitl/netclient:latest
bash-5.1# ls
netclient     netclient.sh
bash-5.1# 
`

I have all the clients running on `testing`

different workflow builds the testing tag..... and it is exactly what it says .... testing... not guaranteed to function properly

better than not having access to my nfs shares tbh

out of topic, but just curious, how are these states determined? all nodes are able to communicate w/ each other

the status is an indication of the mq communications.

warning/error status means the node in question is not being kept in sync with the server

I was hosting on gcp but that's 240ms latency away so decided to bring the server closer to me

<@816758878980276224> wont it fail if node cant ping the server? could be that ICMP is disabled

Interesting, is ICMP required? This particular server does not have ICMP enabled.

im guessing that's the issue, at least think we've encountered it in the past

so I enabled ICMP and recreated the containers with an older stable version

no more errors in netclient logs or in the server's traefik<->mqtt logs

Nice! We need to update docs to make sure that’s explicit