Skip to content

Common Errors (while developing)

Jump to bottom
Harshit Garg edited this page Sep 20, 2022 · 1 revision

There are some common errors you may encounter while developing or setting up vSwarm, that may be caused by a go module versioning or problems otherwise unrelated to vSwarm itself. Use this doc for help, otherwise contact the maintainer or file an issue.

Common errors

  • If you get unknown revision error (@v0.0.0-00010101000000-000000000000: invalid version: unknown revision 000000000000), check the package name, import path, module name again. The package name is probably not supposed to be a URL (make it a path instead), module name can be.

  • Check your go version, go version in files, GO111MODULES is on or not, your directory containing go.mod file is added in go.work or not.

  • If problems with gopls, check go.work, check gopls settings.

  • If you upgrade a module's version and there are new errors, go to pkg.go.dev, see the changes made between working version and new version, see the changelog on github, and modify accordingly.

  • https://stackoverflow.com/questions/57722865/go-modules-pulls-old-version-of-a-package

  • Check the architecture of your machine (Should be x86 and not ARM)

  • https://stackoverflow.com/questions/57700860/error-protoc-gen-go-program-not-found-or-is-not-executable

  • If you are not going to use firecracker microvm, be sure to explicitly specify this while setting up and creating the node. For instance,

Setup node

# This may throw some errors, about Invalid argument. That's fine.
./scripts/cloudlab/setup_node.sh stock-only

Start cluster

# This will take some time
./scripts/cluster/create_one_node_cluster.sh stock-only

Docs

Clone this wiki locally