[Server] Meshery Adapter Deployments

[leecalcote]

Current Behavior

Meshery Server is unable to undeploy Meshery Adapters.

Screenshots/Logs

time="2023-07-12T17:04:32Z" level=info msg="Undeploying Adapter" app=meshery
changing adapter status of meshery-osm on port 10009 to status DISABLED
time="2023-07-12T17:04:32Z" level=info msg="Failed to Undeploy adapter" app=meshery
time="2023-07-12T17:04:32Z" level=error msg="Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?" app=meshery code=2259 probable-cause= severity=3 short-description="Unable to create new kube client" suggested-remediation=

Environment

• Host OS: Linux (Ubuntu)
• Platform: Docker
• Meshery Server Version: stable-v0.6.107

---

Contributor Guides and Handbook

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Meshery UI in Figma
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

[Shaman20]

Hey @leecalcote I am know basics of golang, docker and kubernetes and was looking for meshery server issues. Can I work on this issue as my first

[leecalcote]

I very much appreciate this request @Shaman20. However, no, this is not a beginner issue and you need more support than you realize. The lack of "help wanted" label is intentional, because of the nature of this.

[leecalcote]

@nebula-aac it's showtime.

[nebula-aac]

still researching, i saw the error popped up, testing some changes

[leecalcote]

It's good to be aware of docker context @nebula-aac

[nebula-aac]

Yes the error occurred when in the Kubernetes context. I'm testing to check for docker versus kubernetes platforms before the deployment happens

[leecalcote]

We're still chasing down the goal of a slim default profile.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.