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
{{ message }}
This repository has been archived by the owner on Oct 27, 2021. It is now read-only.
Actually, COMPOSE_FILE is exported everywhere in the script. Indeed, with a clean console, I can run . ./start-stack.sh and see that COMPOSE_FILE is populated after the script is run. In what environment & use case did you see this @dixonwhitmire ?
@ccorley Thanks for taking a look! I will retest to see if I can duplicate. This may have been a case where I tried to execute the command from "the wrong tab"
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Please review the ./start-stack.sh script to determine why the docker compose COMPOSE_FILE variable isn't populated when start-stack.sh completes
The text was updated successfully, but these errors were encountered: