Current Behavior
When running go mod tidy in MeshKit, several tests fail with errors like:
github.com/docker/docker/api@v1.54.0: parsing go.mod:
module declares its path as: github.com/moby/moby/api
but was required as: github.com/docker/docker/api
These errors occur in dependencies such as github.com/kubernetes/kompose and github.com/fsouza/go-dockerclient.
Expected Behavior
All tests should run successfully with go test ./... without any module path mismatches, even when the code itself hasn’t changed.
Screenshots/Logs
# github.com/meshery/meshkit/utils/kubernetes/kompose imports
github.com/kubernetes/kompose/client imports
github.com/kubernetes/kompose/pkg/app imports
github.com/kubernetes/kompose/pkg/transformer imports
github.com/fsouza/go-dockerclient imports
github.com/docker/docker/api/types/registry: github.com/docker/docker/api@v1.54.0: parsing go.mod:
module declares its path as: github.com/moby/moby/api
but was required as: github.com/docker/docker/api
Environment
- Host OS: Windows 11
- Platform: (tested locally)
- Meshery Server Version: N/A (MeshKit library)
- Meshery Client Version: N/A (MeshKit library)
Suggested Fix / Notes
Adding a replace directive in go.mod appears to resolve this:
replace github.com/docker/docker/api => github.com/moby/moby/api v20.10.24+incompatible
This allows Go to reconcile the module path mismatch without changing MeshKit source code.
Current Behavior
When running
go mod tidyin MeshKit, several tests fail with errors like:These errors occur in dependencies such as
github.com/kubernetes/komposeandgithub.com/fsouza/go-dockerclient.Expected Behavior
All tests should run successfully with
go test ./...without any module path mismatches, even when the code itself hasn’t changed.Screenshots/Logs
Environment
Suggested Fix / Notes
Adding a
replacedirective ingo.modappears to resolve this:This allows Go to reconcile the module path mismatch without changing MeshKit source code.
Contributor [Guides](https://docs.meshery.io/project/contributing) and [Handbook](https://meshery.io/community#handbook)
🛠 [Meshery Build & Release Strategy](https://docs.meshery.io/project/contributing/build-and-release)
📚 [Instructions for contributing to documentation](https://github.com/meshery/meshery/blob/master/CONTRIBUTING.md#documentation-contribution-flow)
🎨 Wireframes and [designs for Meshery UI](https://www.figma.com/file/SMP3zxOjZztdOLtgN4dS2W/Meshery-UI) in Figma [(open invite)](https://www.figma.com/team_invite/redeem/GvB8SudhEOoq3JOvoLaoMs)
🙋🏾🙋🏼 Questions: [Discussion Forum](http://discuss.meshery.io) and [Community Slack](https://slack.meshery.io)