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
$ cat printenv.sh
echo $MY_VAR
# in host
$ MY_VAR=test ./printenv.sh
test
$ MY_VAR=test limactl shell default ./printenv.sh
# print nothing
# in guest
$ MY_VAR=test ./printenv.sh
test
So the environment variables are not passed through by limactl shell today. Is this the expected behaviour? If so, I'm interested to learn the reason of it.
I'm aware of Lima yaml has a field to pass env var but seems it can only be populated one time during booting, instead of passing-through in each limactl shell command.
limactl shell is just establishing an ssh connection. You would have to configure both the client and the server side to allow transfer of an environment variable.
An easier way is to just assign the variable explicitly in your remote command:
Description
So the environment variables are not passed through by
limactl shell
today. Is this the expected behaviour? If so, I'm interested to learn the reason of it.I'm aware of Lima yaml has a field to pass env var but seems it can only be populated one time during booting, instead of passing-through in each
limactl shell
command.Context of my use case.
The text was updated successfully, but these errors were encountered: