“fatal error: concurrent map iteration and map write”
“dial tcp: lookup meshery on 127.0.0.11:53: no such host”
“meshery-meshery-kuma-1 | /meshery-kuma: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34’ not found (required by /meshery-kuma)”
Hi @weilirs, it looks like we’re having a challenge with Meshery’s Adapter for Kuma. Let’s remove that adapter from your deployment for the time being, so that you can have a fully healthy deployment.
You’re running Docker Desktop for Mac without Kubernetes enabled, is that right? To confirm, you can run mesheryctl system context view and verify the value for platform. It’ll be either kubernetes or docker. If you see meshery-kuma and other adapters listed in components, let’s remove those and start with just Meshery Server for the moment. Start by executing mesheryctl system stop.
First, will you confirm that you’re using a mesheryctl of v0.7.100+ by executing mesheryctl version? If your client version is less than v0.7.100, please upgrade mesheryctl.
Second, create a new context by executing mesheryctl system context create docker -p docker (assuming that your using Docker as you platform to deploy Meshery).
Third, switch to your new context by executing mesheryctl system context switch docker. Confirm that you have no components (adapters) listed in your new context. You should see the empty set [] as the value for components.
FYI, you can list all contexts and your currently selected context using mesheryctl system context list.
Fourth, start your Meshery deployment by executing mesheryctl system start (having switched to your new context).
You should now have a running Meshery Server deployment without any Adapters.
