[06:02] <eraserpencil> does anyone know if there's a gadget snap for the Nvidia TX2 available?
[11:28] <mup> PR snapd#5508 opened: cmd/snap: print unset license as "unset", instead of "unknown <Created by chipaca> <https://github.com/snapcore/snapd/pull/5508>
[12:13] <mup> Bug #1781789 opened: The main docs https://docs.snapcraft.io/core/ don't mention snapctl <Snappy:New> <https://launchpad.net/bugs/1781789>
[12:16] <MrJones> side remark: why is the tool named snap, the page snapcraft but the package snappy? that is quite confusing
[12:16] <mup> 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) <Snappy:New> <https://launchpad.net/bugs/1781790>
[12:17] <MrJones> I want to start kubelet as packaged in snap, and tried this: snapctl start kubelet
[12:17] <MrJones> this gives me the error: "error: error running snapctl: cannot start without a context"
[12:17] <MrJones> 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] <mup> 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) <Snappy:New> <https://launchpad.net/bugs/1781790>
[12:18] <MrJones> and in the docs I can't find how to use snapctl either, just how to use the snap command
[12:18] <MrJones> so how does starting a service work? what is this "context" I'm missing?
[12:18] <MrJones> I'm testing this on an ubuntu 18.04 lts install
[12:44] <mup> Bug #1781789 changed: The main docs https://docs.snapcraft.io/core/ don't mention snapctl <Snappy:Invalid> <https://launchpad.net/bugs/1781789>
[13:25] <MrJones> are the kubelet/kubeadm snaps still maintained? because I can't get them to work
[14:56] <cjwatson> 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] <MrJones> cjwatson: yea, it took me a really long time to realize that xD
[16:04] <MrJones> but even doing that, I got errors
[16:04] <MrJones> kubeadm is confused that kubectl isn't run via systemctl and complains the kubelet port is used up
[16:05] <MrJones> and when I make it ignore the error, it times out on something
[16:06] <MrJones> 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] <MrJones> so it seems the kubelet/kubeadm snap packages simply aren't packaged in a working state right now
[19:43] <mup> Bug #1781789 opened: snapctl doesn't advertise that it's an internal tool <Snappy:New> <https://launchpad.net/bugs/1781789>
[19:49] <mup> PR snapcraft#2180 opened: code: use black as the standard style <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2180>
[20:07] <mup> PR snapd#5465 closed: daemon, overlord/state: warnings pipeline <Created by chipaca> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/5465>
[20:32] <mup> PR snapd#5509 opened: daemon: move to use a constructor for Meta <Created by chipaca> <https://github.com/snapcore/snapd/pull/5509>
[20:39] <mup> PR snapd#5510 opened: daemon, overlord/state: warnings pipeline <Created by chipaca> <https://github.com/snapcore/snapd/pull/5510>