k9s command not found after snap install

[s-bernhardt]

Describe the bug
A simple snap install does not work as expected. The k9s command was not found after installation.

To Reproduce
Steps to reproduce the behavior:

1. Login to ubuntu as regular user (sudoer)
2. Install k9s via snap sudo snap install k9s
3. Run command k9s
4. See error

ubuntu@k9s-node:~$ k9s
Command 'k9s' not found, did you mean:
  command 'kas' from deb kas (2.6.3-2)
Try: sudo apt install <deb name>

5. Binary is available at /snap/k9s/current/bin/k9s

Expected behavior
k9s would start by using the current KUBECONFIG

Versions (please complete the following information):

• OS: [Ubuntu Server 22.04.2 LTS]
• K9s: [0.27]
• K8s: [1.26.5]

Additional context
It is reproducible on any other Ubuntu Server 22.04 instances
Workaround: alias k9s=/snap/k9s/current/bin/k9s

[slimus]

Hello @s-bernhardt-atos! Thanks for your detailed issue. I still work on snap package here. I'm going to close this issue, but you can add details to the existing issue.

[koolvn]

Well actually you can make a soft link to snap's bin directory which is in PATH

sudo ln -s /snap/k9s/current/bin/k9s /snap/bin/

Now k9s works from any terminal instance on your machine

[kmgrime]

Well actually you can make a soft link to snap's bin directory which is in PATH

sudo ln -s /snap/k9s/current/bin/k9s /snap/bin/

Now k9s works from any terminal instance on your machine

Thanks for this, was needed after install on Fedora 38 via Snap.

[ECiurleo]

This fixed the issue for me installing k9s on Ubuntu (via snap store and via CLI)

[raymundovr]

Unfortunately there's one more issue on Ubuntu 22.04 ARM:

$ sudo ln -s /snap/k9s/current/bin/k9s /snap/bin/
$ k9s
bash: /snap/bin/k9s: cannot execute binary file: Exec format error

I've installed k9s by downloading the k9s_linux_arm64.deb file from the releases page and using apt install

[Afaq-DevOps]

Well actually you can make a soft link to snap's bin directory which is in PATH

sudo ln -s /snap/k9s/current/bin/k9s /snap/bin/

Now k9s works from any terminal instance on your machine

Thanks for this, was needed after install on Fedora 38 via Snap.

its work for me

[clbarrett]

Well actually you can make a soft link to snap's bin directory which is in PATH

sudo ln -s /snap/k9s/current/bin/k9s /snap/bin/

Now k9s works from any terminal instance on your machine

Thanks for this, was needed after install on Fedora 38 via Snap.

its work for me

This workaround worked for me.
The underlying issue is still here as of 4/4/2024 though.

[ECiurleo]

#2350

I submitted the fix a while ago but it's not been pushed up to the snap store. Until it is people installing via snap will get the issue.

[clbarrett]

Aah excellent. Thank you ECiurleo. And in the meantime, that command works to fix it so we have a workaround. Awesome!

[raikrahul]

is there a fix yet?

[kmgrime]

is there a fix yet?

Well actually you can make a soft link to snap's bin directory which is in PATH

sudo ln -s /snap/k9s/current/bin/k9s /snap/bin/

Now k9s works from any terminal instance on your machine

Thanks for this, was needed after install on Fedora 38 via Snap.

Seems like its still in a PR, aka not fixed.

[mlliarm]

Still not fixed on Ubuntu 22.04.4, but the workaround of the soft link works great, so thanks !

[ECiurleo]

K9s needs to submit the PR with the fix (that has already been merged) to the snap store. Until then the issue will continue. Sent from Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Michail Liarmako. ***@***.***> Sent: Friday, May 31, 2024 9:52:14 AM To: derailed/k9s ***@***.***> Cc: Emanuele Ciurleo ***@***.***>; Comment ***@***.***> Subject: Re: [derailed/k9s] k9s command not found after snap install (Issue #2128) Still not fixed on Ubuntu 22.04.4. — Reply to this email directly, view it on GitHub<#2128 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACTK3GKRMPLQL67AEWA3XT3ZFBW75AVCNFSM6AAAAAAZEQOWNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBSGA2TSNRTGQ>. You are receiving this because you commented.Message ID: ***@***.***>