https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
f
Is there a question in here somewhere that I missed?
q
am i wrong that 
rdctl
won't tell me what version of RD i'm using?
f
No, you are not wrong
q
😞
f
I thought we had an issue for it, but I can't find it. The closest we have is Create `rdctl info` command to provide non-settings state, like IP address · Issue #5526, so maybe add a comment there?
q
f
One challenge is that I think 
rdctl
should be able to show the version even if the app is not running, so it can't use the API to query it. So it first needs to figure out which installation it should report on (you can have multiple different versions installed), and then get the version information from the VERSIONINFO resource, or the Info.plist etc.
Or I guess we can "burn" the version into the 
rdctl
executable, and it will just always show that version, even when the installed version of Rancher Desktop is different?
q
i have multiple versions installed
so, there's value in telling me the version of the version that last ran
is it more or less looking into a config directory such that when a version runs, it can write "i was version x"?
having "skid marks" is handy
bonus points if it says "I <my path> was version <x>"
f
Copy code
$ grep appVersion ~/Library/Logs/rancher-desktop/settings.log
2024-01-30T17:16:57.340Z: appVersion is 1.12.2-139-gb72edfca
q
having rdctl able to say "hey i'm from rd 2.1.5, but I saw RD 3.9.6 running"
... is helpful
f
Sorry, not going to bother with keeping track of processes that have already finished (beyond what is written to the logs directory). 
rdctl
could display a burned-in version, plus, if the app is running, the actual app version.
q
is it too much to ask it to tell me where the logs directory is? 🙂
or the conf directory for that matter? 🙂
f
And I could see an argument for adding an 
appinfo.log
file if you create an issue for that.
There is an internal command you can use:
Copy code
$ rdctl paths | jq -r .logs
/Users/jan/Library/Logs/rancher-desktop
q
2024-01-28T03:00:54.286Z: appVersion is 1.12.2
"not documented" => "mostly not helpful" 🙂
(currently grumbling about the fact that an undocumented github api is failing in my fork)
f
It is not supposed to be used by users, but I can see that the log directory might be useful
q
yeah, 
rdctl paths
as is isn't the kind of thing to spit at users
the log directory seems like something a user could really need if the app is failing to start
f
In general people should not touch any of the internal directories. I know it is sometimes necessary, but very often it lets them break things that are very hard to figure out.
Like all the time when users try to run 
limactl start
manually against the Rancher Desktop VM (which won't work)
q
yeah, i get it
i can't remember why i ran the command at the start of this thread
"something wasn't working" was definitely my starting point 🙂
(it might have been around when there was a new version of RD available and it was doing a lousy job of downloading faster than a turtle)
f
I do want to create an 
rdctl logs
command that can also zip up the logs, push them to an S3 bucket, and print a UUID that users can paste into a Github report.
q
that sounds lovely
there's one 
Dockerfile
wrapperish thing that has that
i think it had some 
planet
naming thing
f
Because (1) I'm getting tired of getting Github issues without logs, and (2) it feels wrong to ask users to post logs that become world-readable
❤️ 1
👍 1
q
Earthly
i presume you can't really do that w/o posting to an endpoint that has credentials to publish to the bucket
(unless you have a writeonly bucket?)
f
I have a plan how it should work without requiring maintenance: uploads will be deleted after 7 days unless referenced in a GitHub issue, and 3 months after the issue is closed.
🙌 1
The endpoint would be simple https server, that would also trigger the expiration logic
I just need to write it up, figure out where to run it, get the bucket, get read credentials for developers, and then we can write the 
rdctl logs
command, and even link it from the UI.
👍 1
I wish Github allowed filling issue templates from URI query parameters. Or is that a thing by now?
q
um, i'm 76% certain it's a thing?
(lemme go look around?)
so, yeah, you can definitely prefill stuff
f
Awesome! Still needs testing what happens if you are not logged into Github when you invoke the URL
Anyways, this will be a Q2 project, not right now
BTW, please don't post a huge wall of text to the channel (or even in a thread), use a text snippet like this instead.
Untitled.txt
Bonus feature for snippets (beyond being collapsible): you can easily download, view raw, etc...
q
hmm, lemme ask about collapsing
f
The "Create text snippet" action is in the menu for the "+" button in the lower left corner:
q
Yeah yeah, I use it, at times
Open in Slack
PreviousNext
Powered by