You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the host templates {{.Home}} is the host home directory, and in the guest templates it is the guest home directory.
But {{.User}} is always the host user, and not the guest user, which a guest template will have to construct via {{.User}}.linux.
I think the guest templates should have additional variables both for the guest user, and for the host home directory.
I don't have a good suggestion how to deal with naming that doesn't require changing the definition of {{.User}} in the guest templates, which I don't want to do because it breaks compatibility.
What do people think about this:
Variable
Host
Guest
.User
jan
jan
.Home
/Users/jan
/home/jan.linux
.Guest.User
jan.linux
jan.linux
.Guest.Home
/home/jan.linux
/home/jan.linux
.Host.User
jan
jan
.Host.Home
/Users/jan
/Users/jan
I think the {{.Guest.*}} settings are probably never going to be used in host templates, but it doesn't hurt to include them.
The text was updated successfully, but these errors were encountered:
I think the {{.Guest.*}} settings are probably never going to be used in host templates
Currently we are using workarounds such as $HOME and ~ in the template scripts.
The template scripts use the guest template variables. We (intentionally) don't have host scripts. I was talking about the host templates (like copyToHost or hostSocket) not needing access to the guest settings.
But that is potentially good enough
Right now there is no way to figure out the mount point of the host home directory from inside a provisioning script. I guess you can use $USER for the guest username.
You can work around this by using a fixed mount point for the host home, if you need to know the location in the scripts:
mounts:
- location: '~'mountPoint: /mnt/host-home
So I don't know. The thing that triggered me to create this issue was when I realized that {{.User}} in guest templates does not match the value used by {{.Home}}, which feels wrong and confusing to me.
Anyways, we can take some time to think about it because there are work arounds.
In the host templates
{{.Home}}
is the host home directory, and in the guest templates it is the guest home directory.But
{{.User}}
is always the host user, and not the guest user, which a guest template will have to construct via{{.User}}.linux
.I think the guest templates should have additional variables both for the guest user, and for the host home directory.
I don't have a good suggestion how to deal with naming that doesn't require changing the definition of
{{.User}}
in the guest templates, which I don't want to do because it breaks compatibility.What do people think about this:
I think the
{{.Guest.*}}
settings are probably never going to be used in host templates, but it doesn't hurt to include them.The text was updated successfully, but these errors were encountered: