lima-vm / lima-vm/lima

Using --env for nerdctl doesn't pass through current environment values

Open
#412 11 comments 0 reactions 0 assignees View on GitHub
component/nerdctl enhancement expert
Dominant language
Go
Stars
21.9k
Forks
957
Avg merge
2d 6h
Merged PRs (30d)
53

Description

I'm unsure if this is expected behaviour or not, I was attempting to replace `docker` with `nerdctl.lima` on Mac OSX (M1) and almost all other runtime options seem to work the same, so seemed a bit odd that this one doesn't quite get there. Feel free to close if it's expected behaviour.

```
#-❯ export FOO=bar

#-❯ echo $FOO
bar

#-❯ nerdctl.lima run --rm -it -e FOO ubuntu bash
root@4b71f410d6a4:/# echo $FOO

```

vs

```
#-❯ nerdctl.lima run --rm -it -e FOO=baz ubuntu bash
root@1697d3d01eac:/# echo $FOO
baz
```

When using docker, usage of `-e FOO` with no value, would pass through whatever it is in the current environment. Perhaps it's a problem with `lima` not passing through the current environment to the linux VM on mac OS. Perhaps this is expected behaviour of native `nerdctl`? I'll move this issue over to there if that's the case.

FWIW- I'm using the `default` VM that came with `brew install lima`. Perhaps there is a way to configure it so the entire current ENV vars are always pushed through the SSH?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.