In my case the --last-start-only addition end up giving empty file.
with minikube logs -f=log.txt i can see logs being added there.

with minikube logs -f=log.txt i can see logs being added there.

couldn't quite get what you mean, -f is a shorthand for --follow. I'm guessing you mean --file=filename? in that case I agree, the issue is only present if --last-start-only is added, though I still haven't checked it with other flags added.

I suspect it's just just an issue with --last-start-only overriding the --file flag and causing the output to still go to stdout instead of a file. I'll have to check the code to verify that, but I don't have the time for it at the moment...

Hi @mattisafur Just for reference, this is the implementation of the flag --last-start-only: https://github.com/kubernetes/minikube/blob/master/cmd/minikube/cmd/logs.go#L80
If i find something regarding over-riding the --file flag i'll inform here

I looked at the implementation. at the moment it does the following (when --file is set):

flowchart

A{--last-start-only set?} --> |true| B[print start log to stdout]
A --> |false| C
C{--audit set?} --> |true| D[print audit log to stdout]
C --> |false| E[print both audit log and last start log to file]

It makes more sense to me that will will work based on these rules:

• if --file <filepath> is specified, output to file instead of stdout
• if --audit is specified, output only the audit log
• if --last-start-only is specified, output only the last-start log

(handle a case where both --audit and --last-start-only are specified? maybe just output nothing?)

I'll make a PR for this change.