k9s: k9s snap release wont start

Describe the bug A clear and concise description of what the bug is.
22:21:56 θ67° [rolf:~] $ snap info k9s
name: k9s
summary: K9s is a CLI to view and manage your Kubernetes clusters.
publisher: Fernand Galiana (derailed)
contact: fernand@imhotep.io
license: unset
description: |
K9s is a CLI to view and manage your Kubernetes clusters.
By leveraging a terminal UI, you can easily traverse Kubernetes resources
and view the state of you clusters in a single powerful session.
commands:
- k9s
snap-id: IIsGjhjg5ghn6VAZFbferlrrh4zy2kO9
tracking: stable
refresh-date: today at 22:20 CEST
channels:
stable: 0.7.7 2019-06-14 (126) 9MB -
candidate: ↑
beta: ↑
edge: 0.5.1 2019-04-19 (99) 9MB devmode
installed: 0.7.7 (126) 9MB -
22:22:07 ⌂69% θ64° [rolf:~] $ whereis k9s
k9s: /snap/bin/k9s
22:22:20 ⌂64% θ64° [rolf:~] $ k9s
____ __.________
| |/ _/ __ \______
| < \____ / ___/
| | \ / /\___ \
|____|__ \ /____//____ >
\/ \/
Boom!! Refine Config.
22:22:23 ⌂61% θ67° [rolf:~] $
22:25:43 θ64° [rolf:~] $ k9s version
____ __.________
| |/ _/ __ \______
| < \____ / ___/
| | \ / /\___ \
|____|__ \ /____//____ >
\/ \/
Version: 0.7.7
Commit: 2eb817fda8c62c772cfdd0424cbe54706c356f26
Date: 2019-06-14T01:50:05Z
To Reproduce Had 0.7.5 installed. Installed 0.7.7 with snap and got this error. Tried deleting .k9s folder but no difference.
Expected behavior k9s to make awesome Versions (please complete the following information):
- OS: Ubuntu 18.04
- K9s 0.7.7
- K8s 1.14.x
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 2
- Comments: 15 (6 by maintainers)
Commits related to this issue
- Release v0.11.0 * [PR #243](https://github.com/derailed/k9s/pull/243) Invalid value for --force-exit-zero * [PR #241](https://github.com/derailed/k9s/pull/241) Add a non-root user in docker image * [... — committed to derailed/popeye by derailed a year ago
- Release v0.11.0 * [PR #243](https://github.com/derailed/k9s/pull/243) Invalid value for --force-exit-zero * [PR #241](https://github.com/derailed/k9s/pull/241) Add a non-root user in docker image * [... — committed to derailed/popeye by derailed a year ago
- Release v0.11.0 * [PR #243](https://github.com/derailed/k9s/pull/243) Invalid value for --force-exit-zero * [PR #241](https://github.com/derailed/k9s/pull/241) Add a non-root user in docker image * [... — committed to derailed/popeye by derailed a year ago
- Release v0.11.0 * [PR #243](https://github.com/derailed/k9s/pull/243) Invalid value for --force-exit-zero * [PR #241](https://github.com/derailed/k9s/pull/241) Add a non-root user in docker image * [... — committed to mercedes-benz/popeye by derailed a year ago
To start k9s with snap on Ubuntu 18.04 I had to manually create
~/.k9s
and run it withk9s --kubeconfig ~/.kube/config
This worked for me. Is there a way of embedding that config into
k9s
so that we don’t have to type it every time?Ah, too bad @derailed, thanks for explanation! Will try installation from source. Update: edge installation worked
snap install k9s --edge --devmode
as mentioned https://github.com/derailed/k9s/issues/166#issuecomment-485059530Have the same issue on Ubuntu 18.04, also I tried to follow https://github.com/derailed/k9s/issues/240#issuecomment-505823987 suggestion, I still got:
If I take a look at logs there seam to be permission/ownership issue:
Anyhow
/home/anita/.kube/config
is owned by same user ask9s
and permissions seam legit… maybe someone experienced same?@roflmao @lukaszo @joskfg - the interaction with the snap folks is taking forever. Think you should give LinuxBrew install instead. Can you give 0.7.13 a rinse? Thank so very much for all your reports!
@roflmao Thank you for sending this! Could you do me a favor and try the following provided you’re using a std kuconfig setup. Thank you!!