Skip to content
This repository has been archived by the owner on Oct 27, 2021. It is now read-only.

COMPOSE_FILE variable isn't populated after ./start-stack.sh is executed #420

Open
dixonwhitmire opened this issue Jan 29, 2021 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@dixonwhitmire
Copy link
Member

Please review the ./start-stack.sh script to determine why the docker compose COMPOSE_FILE variable isn't populated when start-stack.sh completes

@dixonwhitmire dixonwhitmire added the bug Something isn't working label Jan 29, 2021
@ccorley
Copy link

ccorley commented Feb 8, 2021

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 ccorley self-assigned this Feb 8, 2021
@ccorley ccorley added this to the Sprint 2/8 - 2/19 milestone Feb 8, 2021
@dixonwhitmire
Copy link
Member Author

@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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants