[06:02] does anyone know if there's a gadget snap for the Nvidia TX2 available? [11:28] PR snapd#5508 opened: cmd/snap: print unset license as "unset", instead of "unknown [12:13] Bug #1781789 opened: The main docs https://docs.snapcraft.io/core/ don't mention snapctl [12:16] side remark: why is the tool named snap, the page snapcraft but the package snappy? that is quite confusing [12:16] Bug #1781790 opened: snapctl start gives error message that is useless to beginners, and nothing of it is explained in --help or a man page (which doesn't seem to exist) [12:17] I want to start kubelet as packaged in snap, and tried this: snapctl start kubelet [12:17] this gives me the error: "error: error running snapctl: cannot start without a context" [12:17] I odn't know what that means, and as you can see by the ticket I just filed ( #1781790 ) neither --help nor man snapctl explain it [12:17] Bug #1781790: snapctl start gives error message that is useless to beginners, and nothing of it is explained in --help or a man page (which doesn't seem to exist) [12:18] and in the docs I can't find how to use snapctl either, just how to use the snap command [12:18] so how does starting a service work? what is this "context" I'm missing? [12:18] I'm testing this on an ubuntu 18.04 lts install [12:44] Bug #1781789 changed: The main docs https://docs.snapcraft.io/core/ don't mention snapctl [13:25] are the kubelet/kubeadm snaps still maintained? because I can't get them to work [14:56] MrJones: Did you try just "snap start kubelet"? As I understand it (I work on the server side of things - not a snapd hacker myself), snapctl is meant for use by package hooks and things rather than being something users are supposed to run directly [16:04] cjwatson: yea, it took me a really long time to realize that xD [16:04] but even doing that, I got errors [16:04] kubeadm is confused that kubectl isn't run via systemctl and complains the kubelet port is used up [16:05] and when I make it ignore the error, it times out on something [16:06] oh and it lacks crictl which needs to be installed separately (but no apt or snap is available, so it's not that easy to do) [16:06] so it seems the kubelet/kubeadm snap packages simply aren't packaged in a working state right now === grumble1 is now known as grumbe === grumbe is now known as grumble === devil is now known as Guest78677 === Guest78677 is now known as devilz === devilz is now known as devil_ === devil_ is now known as devilz === devilz is now known as devilzz === devilzz is now known as devil_ [19:43] Bug #1781789 opened: snapctl doesn't advertise that it's an internal tool [19:49] PR snapcraft#2180 opened: code: use black as the standard style [20:07] PR snapd#5465 closed: daemon, overlord/state: warnings pipeline [20:32] PR snapd#5509 opened: daemon: move to use a constructor for Meta [20:39] PR snapd#5510 opened: daemon, overlord/state: warnings pipeline