Add {{.TempDir}} and {{.GlobalTempDir}} variables to host templates#3318
Add {{.TempDir}} and {{.GlobalTempDir}} variables to host templates#3318AkihiroSuda merged 1 commit intolima-vm:masterfrom
Conversation
89857c8 to
1f6fd20
Compare
|
Do you need to model "the real" $TMPDIR, or should it be something like $LIMA_TEMP instead? One concern was that there are many users sharing the |
|
This made default.yaml compatible with Windows. I managed to create and start VM w/o changes to template. Output of the mount command: The |
|
9p mounts |
|
I'm going to leave this PR open (and in draft mode) because I think adding the But the change to |
f76cd2f to
cb47c5b
Compare
|
I've rebased this PR on latest This PR does introduce a user-visible change, in that I'm undecided if this is acceptable or not. |
I assume you meant Unix, not macOS.
How about we use On Windows both variables would be the same. |
To me this sounds like the former one is a file and the latter one is a directory |
|
How about The PS: I think I actually prefer |
👍 |
cb47c5b to
0e6e56d
Compare
Allows writing the temp mount as
mounts:
- location: "{{.Temp}}/lima"
mountPoint: /tmp/lima
Note that on macOS this would use $TMPDIR and not /tmp, so would be a change
in behaviour. It would not affect existing instances though.
Signed-off-by: Jan Dubois <jan.dubois@suse.com>
0e6e56d to
67a3361
Compare
Allows writing the
/tmp/limamount asNote that on macOS this would use
$TMPDIRand not/tmp, so would be a change in behaviour. It would not affect existing instances though.