Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install-script fails because of missing unzip #1337

Closed
okin opened this issue May 3, 2021 · 2 comments · Fixed by #1435
Closed

Install-script fails because of missing unzip #1337

okin opened this issue May 3, 2021 · 2 comments · Fixed by #1435
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@okin
Copy link
Contributor

okin commented May 3, 2021

What happened:

I wanted to install KubeOne through the oneliner from the documentation.
It failed because my system was missing unzip.

ubuntu@kubeone:~$ curl -sfL get.kubeone.io | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   637  100   637    0     0   2757      0 --:--:-- --:--:-- --:--:--  2757
100 10.4M  100 10.4M    0     0  9279k      0  0:00:01  0:00:01 --:--:-- 15.1M
Copying kubeone binary into /usr/local/bin
sh: 36: unzip: not found

What is the expected behavior:

It installs fine.
If unzip is missing i'd expect me to notify of it and maybe tell me how to make it work (i.e. by a message like "you are missing unzip. Please install and run the command again")

How to reproduce the issue:

Installed on a basic Ubuntu 20.04 image - nothing installed but bare necessities.

Anything else we need to know?

Information about the environment:
KubeOne version (kubeone version): -
Operating system: Ubuntu 20.04
Provider you're deploying cluster on: -
Operating system you're deploying on: -

@okin okin added the kind/bug Categorizes issue or PR as related to a bug. label May 3, 2021
@kron4eg
Copy link
Member

kron4eg commented May 6, 2021

@okin thank you for the report. BTW, we accept contributions.

@kubermatic-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubermatic-bot kubermatic-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 4, 2021
okin added a commit to okin/kubeone that referenced this issue Aug 4, 2021
okin added a commit to okin/kubeone that referenced this issue Aug 4, 2021
Closes kubermatic#1337

Signed-off-by: Niko Wenselowski <der@nik0.de>
kubermatic-bot pushed a commit that referenced this issue Aug 4, 2021
Closes #1337

Signed-off-by: Niko Wenselowski <der@nik0.de>
cedi pushed a commit to cedi/kubeone that referenced this issue Oct 8, 2021
Closes kubermatic#1337

Signed-off-by: Niko Wenselowski <der@nik0.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants