search

zerotier / install.zerotier.com

Source for https://install.zerotier.com curl|bash installer
https://install.zerotier.com
BSD 3-Clause "New" or "Revised" License
62 stars 44 forks source link

Support for Ubuntu 20.04 focal #13

Closed mprasil closed 2 years ago

mprasil commented 4 years ago

This Ubuntu version is going to be released in couple months, daily builds are already available. Maybe we could get support in before it's officially out?

jdevora commented 4 years ago

I upgraded to 20.04 and when I try apt-get update it gives me the error:

Err http://download.zerotier.com/debian/bionic eoan Release
  404  Not Found [IP: 35.244.178.109 80]
E: The repository 'http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu focal Release' does not have a Release file.
E: The repository 'http://download.zerotier.com/debian/bionic eoan Release' does not have a Release file.
W: Failed to fetch http://download.zerotier.com/debian/bionic/dists/eoan/Release: 404  Not Found [IP: 35.244.178.109 80]
GMDSantana commented 4 years ago

I upgraded to 20.04 and when I try apt-get update it gives me the error:

Err http://download.zerotier.com/debian/bionic eoan Release
  404  Not Found [IP: 35.244.178.109 80]
E: The repository 'http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu focal Release' does not have a Release file.
E: The repository 'http://download.zerotier.com/debian/bionic eoan Release' does not have a Release file.
W: Failed to fetch http://download.zerotier.com/debian/bionic/dists/eoan/Release: 404  Not Found [IP: 35.244.178.109 80]

@jdevora Try using "http://download.zerotier.com/debian/bionic bionic" rather than "http://download.zerotier.com/debian/bionic eoan"

Timple commented 4 years ago

But 20.04 is not bionic right? It should be focal

mprasil commented 4 years ago

Focal has been out for couple months and it's the current latest LTS Ubuntu release. Can we get some update for this?

ghaschel commented 4 years ago

Zerotier is misbehaving a lot lately in 20.04. It sometimes work, sometimes doesn't.

It bugs a lot in a machine with a clean 20.04 install. Doesn't bug at all in a machine which was upgraded from 19 to 20.

Halfwalker commented 3 years ago

Still waiting for a 20.04/focal repo and release. My ansible playbooks have needless complexity to accommodate a focal system with a non-focal (bionic) zerotier release.

asper-ru commented 3 years ago

Still nothing new, eh?

I've fixed installation parameters in my chef recipes and ansible playboosk to use ubuntu 19.04 repo, but it's strange to do not support Ubuntu 20 yet, it's almost 2021 now! Especially strange cause Zerotier just have reduced free limits to 50 nodes and wants money for larger networks, but does it look like the pay service now?

TeoTN commented 3 years ago

It seems it might be easier to use Nebula rather than waiting for support for Focal

nukebloodaxe commented 3 years ago

@asper-ru I suspect most of their resources are allocated to the version 2 release, and this current release is not being maintained as closely as it should be. Given new customers before the 2.0 release will be attempting to use this version, I believe they should at least fix these install issues so people can see it is a product they want to buy; something which does not install will not inspire confidence in a business researcher, and will likely stop them from looking again, even if 2.0 comes out, as hey will have moved on to testing competing products [simple psychology.]

ukd1 commented 3 years ago

This is kind of a joke it's broken for this long. Are y'all supporting this at all anymore?

einverne commented 2 years ago

Still waiting for the support for 20.04

sebzur commented 2 years ago

@adamierymenko @laduke @glimberg Any chances for 20.04?

sebzur commented 2 years ago

OK, I've found snap option: https://snapcraft.io/zerotier - it worked. However, under https://www.zerotier.com/download/ there's no mention about it. Is it okay or rather one should use curl|bash installation (it seems to be the preferred way: https://github.com/zerotier/install.zerotier.com)?

mprasil commented 2 years ago

To quote myself from 2y ago:

This Ubuntu version is going to be released in couple months, daily builds are already available. Maybe we could get support in before it's officially out?

There are already 22.04 daily builds available. The fact that there's still no 20.04 (focal) support in the install script is a bit sad, is there any PR I could submit somewhere to help you resolve that?

alyandon commented 2 years ago

@mprasil I too have been waiting for a while now and it really seems to me like this is a dead sub-project. The last commit in this repository was in 2019 and PRs that were opened to clean up and improve the installer have been open since 2018. If ZT isn't actually building and packaging .debs for newer Ubuntu releases then it seems like building from source is the only viable solution.

adamierymenko commented 2 years ago

It's not abandoned, but it hasn't been updated often. We can test on focal.

adamierymenko commented 2 years ago

A quick test on focal seems to work. Can someone give more information?

joseph-henry commented 2 years ago

OK, I've found snap option: https://snapcraft.io/zerotier - it worked. However, under https://www.zerotier.com/download/ there's no mention about it. Is it okay or rather one should use curl|bash installation (it seems to be the preferred way: https://github.com/zerotier/install.zerotier.com)?

Yes. This works on Focal. Though there's a known issue with Snap's network security policy that prevents outbound connections sometimes. I'll have to speak with them about how to resolve that.

And to expand further on what adam said, this isn't abandoned. Part of our team uses this on latest Ubuntu as daily drivers. Now we could do a better job making official releases for each Ubuntu version, that much is true.

adamierymenko commented 2 years ago

In the past we have often defaulted to using the most recent named release on newer releases if it works fine, so that explains "focal" getting "bionic" etc. You do not necessarily need to build new binaries for every single release.

alyandon commented 2 years ago

Interesting, I just provisioned a Ubuntu 20.04.3 LTS VM and ran the script. It appeared to complete successfully and generated the node ID.

However, the end result is the following in /etc/apt/sources.list.d/zerotier.list

deb http://download.zerotier.com/debian/bionic bionic main

So it looks like it installed the bionic package on focal - which probably works only because 18.04 vs 20.04 are similar enough. Additionally, http://download.zerotier.com/debian/focal appears to not exist which implies ZT isn't building and publishing a focal package.

adamierymenko commented 2 years ago

Yeah we're not yet. We haven't a need to add it unless the older package has issues on focal. Maybe we should use some kind of generic naming convention to keep people from seeing a different distribution name in there and thinking it means something.

alyandon commented 2 years ago

If it works and is supported then I'm fine. For what it is worth - I don't envy you having to package things for a bazillion different distros - it's a lot of work.

adamierymenko commented 2 years ago

We package things for N distributions times many different architectures. It is a lot of work and makes builds very slow. There's no need to add new ones when it's not necessary, but I will give some thought to generic "revision categories" or something similar. Not sure exactly how to solve this issue. It makes supporting Linux really painful sometimes.

mprasil commented 2 years ago

You could also look into discontinuing support for EOL Ubuntu releases like zesty, artful or precise. These have been EOL for years now. If it would free up some bandwidth to properly support current LTS versions, I'd say it is a worthy compromise.

alyandon commented 2 years ago

@mprasil Based on the discussion, it seems like they are just names in the script and don't really reflect support for a particular Ubuntu release. Just like bionic in the repo URL is apparently not specifically meant to imply support for only bionic - it was merely the latest LTS when they wrote the script and ZT moving to a generic repo name would fix that confusion.

Did you see above where I ran the installer script on a fresh 20.04 VM and it was successful? Are you still getting the same error you reported?

mprasil commented 2 years ago

So I'm actually not using these scripts at all. There are places where I deploy in more automated fashion like with Ansible and it's just pain to have exception for specific releases, because there is no package in the repository for specific distribution version.

For example (this is a role that I'm not actually using, but it demonstrates the problem well) this code here is just to work around the problem.

Now granted, this is not a huge problem considering the package otherwise works well on the system, but it looks quite confusing. (even more so in the apt configuration file that ends up on the machine) And considering Ubuntu 20.04 is probably the number 1 most used distribution release in the cloud (or at least near the top) it looks weird that this kind of release isn't directly supported. Especially if it sounds like some alias in Debian repository is all that's really needed.

When I originally reported the issue, 20.04 wasn't yet released, so I reported this with hope that this will be resolved before that LTS version was out and added a workaround "for the time being". I could imagine some new users might try to just add the repo, get an 404 for their distribution and move on to some other product thinking it's unsupported.

sebzur commented 2 years ago

When I originally reported the issue, 20.04 wasn't yet released, so I reported this with hope that this will be resolved before that LTS version was out and added a workaround "for the time being". I could imagine some new users might try to just add the repo, get an 404 for their distribution and move on to some other product thinking it's unsupported.

And that precisely was my first thought... The project is not well supported... What a pity.. The status of this official recommended installation procedure for U20.04 have not only surprised me but disappointed as well. I'm at the moment of important decision - ZeroTier or WireGuard? The two are the sexiest candidates to upgrade the security of our huge network of distributed end-points. I love the idea behind ZT. That's why I decided to give it a second chance and experiment with snap (which after so many years with apt is still somehow unfamiliar for me...) Anyway - do you remember that big title on your front-page?

obraz

(Sorry for beeing so expressive - but I - and I guess everybody - would love if the ZT in U20.04 will just work)

But... But wait.. @alyandon - have you changed anything lately... I just wanted to experiment with your answer here: https://github.com/zerotier/install.zerotier.com/issues/13#issuecomment-1026267490 - but before that, on my another U20.04 device I first tried curl -s https://install.zerotier.com | sudo bash... And... It just worked!. Hurrra!

obraz

@alyandon any comments on that?

alyandon commented 2 years ago

@sebzur I didn't change anything. I provisioned an Ubuntu 20.04.3 VM and ran the very same script you ran which resulted in a working install of ZT for me.

sebzur commented 2 years ago

@alyandon - so probably this is somehow related to this comment: https://github.com/zerotier/install.zerotier.com/issues/13#issuecomment-668595790

On my home-office host I have Ubuntu upgraded multiple times for a few years. Not sure what wash the first U version there... My first comment here https://github.com/zerotier/install.zerotier.com/issues/13#issuecomment-1018994233 was related to the fault installation on my laptop - I bought it something like a year or so ago. Chances are that I had 20 installed there for a first time.

EDIT: I've just tried to install ZT (again) on my laptop - nothing changed. The message says that (...) there may not be a package for your arch.

alyandon commented 2 years ago

@sebzur

Let's try some basic troubleshooting steps then.

  1. Since your laptop is running Ubuntu cat the contents of /etc/lsb-release and post that.
  2. Try running this slightly modified command: curl -s https://install.zerotier.com | sudo bash -x and post that as well.
sebzur commented 2 years ago

@alyandon - thank you for your engagement. During the analysis of curl -s https://install.zerotier.com | sudo bash -x I've noticed that I had local problem with some missing pubkeys (NO_PUBKEY GPG error). I should have noticed it earlier! I was trying to add the keys manually (i.e. for ZT using sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 1657198823E52A61) which failed...

After some investigation I found, that there was some problematic gpg key (the error said gpg: invalid key resource URL '/tmp/apt-key-gpghome.GOWinQfCit/home:cabelo.asc.gpg') - I've simply deleted it (sudo rm /etc/apt/trusted.gpg.d/home\:cabelo.asc), then again processed sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 1657198823E52A61 which succeeded.

After that, again standard ZT installation step with sudo curl -s https://install.zerotier.com | sudo bash ... and it worked as promised on ZT front page :exclamation: :heart:

So it looks (at least in my case) that the only problematic case was my inattention and some mess in the system. Sorry for this dramatic post here https://github.com/zerotier/install.zerotier.com/issues/13#issuecomment-1035588764 And thank you again for the whole work here with the ZT

Anyway - to summarize my problem and leave something potentially useful for someone - if you got stuck at that installation step, check:

alyandon commented 2 years ago

Oh cool - glad you were able to get that working. ZT probably needs to update the installer script to validate the repo key is actually accessible via GPG.

mprasil commented 2 years ago

Not sure when the change happened (probably sometimes end of April looking at the file dates), but now I can see there is repository for 20.04 (focal) and even for recently released 22.04 (jammy) available. Thanks a lot for that folks, I think we can consider this issue resolved.

Whoever worked on this, you made my life a little bit easier, thank you again.