# Rancher CLI up command help

**URL:** <https://forums.suse.com/t/rancher-cli-up-command-help/7054>\
**Category:** Rancher 1.x\
**Created:** [August 8, 2017, 2:32pm UTC](https://forums.suse.com/t/rancher-cli-up-command-help/7054 "2017-08-08T14:32:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stefan-Pamparau](https://avatars.discourse-cdn.com/v4/letter/s/cc9497/32.png) [@Stefan-Pamparau](https://forums.suse.com/u/Stefan-Pamparau)\
**Post date:** [August 8, 2017, 2:32pm UTC](https://forums.suse.com/t/rancher-cli-up-command-help/7054/1 "2017-08-08T14:32:05Z")

</div>

Hello,

I am using the Rancher CLI in order to create stacks using the **up** command.

I am a little bit confused as to why the **up** command is interactive all the time (prompts for inputs to rancher-compose.yml questions) even though I specify an **env** file using the **-e** flag. I need it to not be interactive because I use it from a bash script which must run in a non-interactive way.

Is this the normal behaviour or am I missing something? Also is there another command to create stacks and wait for their start (the stacks create command is non blocking).

Thanks for your help.
