# One-off commands get invalid env

**URL:** <https://community.convox.com/t/one-off-commands-get-invalid-env/461>\
**Category:** Rack (Version 2)\
**Created:** [March 20, 2019, 2:28pm UTC](https://community.convox.com/t/one-off-commands-get-invalid-env/461 "2019-03-20T14:28:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![robert](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@robert](https://community.convox.com/u/robert)\
**Post date:** [March 20, 2019, 2:28pm UTC](https://community.convox.com/t/one-off-commands-get-invalid-env/461/1 "2019-03-20T14:28:01Z")

</div>

I’m not sure if its fully supported, docs are confusing, but it seems like when running a one-off command on a local rack it does not include the env vars.

Or rather, it seems to get env vars as long as they are not defined on the service.

With a convox.yml like this:

```auto
services:
  abc:
    image: nginx
    environment:
      - A=
      - B=b

```

```auto
convox apps create
convox env set A=a B=bb C=c
convox run abc --release `convox build --id` -- env

```

Notice how the environment has

```auto
A=
B=b
C=c

```

I expected that they would be what was set before:

```auto
A=a
B=bb
# no C as it was not specified in the service whitelist.

```