Misleading node install instructions on Mystnodes for Debian <12 and Ubuntu LTS <22
vip72-btw opened this issue · 2 comments
The current node install instructions given to users after registration on Mystnodes are incorrect (these one gets by navigating "Set up node" -> "Desktop" -> "Linux" on the page that shows instructions for running a node for Debian Linux users).
Following these instructions currently won't let you run a node on the following Linux distributions (personally tested):
- Debian 10 (Buster)
- Debian 11 (Bullseye)
- Ubuntu 18.04.6 LTS (Bionic Beaver)
- Ubuntu 20.04.6 LTS (Focal Fossa)
The reason is a required libc6 version mismatch:
# myst
myst: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by myst)
myst: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by myst)
The exactly same errors happen when installing the Mysterium Node from the current 1.29.2 release's .deb package (myst_linux_amd64.deb) on the above mentioned Linux distributions.
Note also that the same instructions are present when navigating to "Set up node" -> "Data center" on the page that shows instructions for hosted Linux instances.
The only solution currently is to either use the myst binary from the release's myst_linux_amd64.tar.gz archive or compiling the node from sources.
To whoever builds these amd64 .deb packages:
See cgo-enabled binary built with Ubuntu 22.04 is incompatible with Ubuntu 20.04 #57328 and this reply golang/go#57328 (comment) that contains a possible solution (setting CGO_ENABLED to 0)
Meanwhile these .deb packages are broken, you should instruct users on Mystnodes to get the node binaries from myst_linux_amd64.tar.gz or alternatively indicate that only Ubuntu >=22 and Debian >=12 are supported for installing from PPA or .deb.
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.
This issue has been automatically closed because it has not had activity for a long time. If this issue is still valid, please ping a maintainer and ask them to label it as "pinned". Thank you for your contributions.