Skip to content
This repository has been archived by the owner on May 26, 2022. It is now read-only.

"docker-compose up" fails to start. #60

Closed
arel opened this issue Apr 6, 2020 · 1 comment
Closed

"docker-compose up" fails to start. #60

arel opened this issue Apr 6, 2020 · 1 comment

Comments

@arel
Copy link
Contributor

arel commented Apr 6, 2020

Starting the grand-stack-starter via docker-compose up fails to start the react app with the following error:

ui_1     | 
ui_1     | > grand-stack-starter-ui-react@0.0.1 start /app
ui_1     | > react-scripts start
ui_1     | 
ui_1     | [HPM] Proxy created: /  -> http://api:4001/graphql
ui_1     | ℹ 「wds」: Project is running at http://172.20.0.4/
ui_1     | ℹ 「wds」: webpack output is served from 
ui_1     | ℹ 「wds」: Content not from webpack is served from /app/public
ui_1     | ℹ 「wds」: 404s will fallback to /
ui_1     | Starting the development server...
ui_1     | 
grand-stack-starter_ui_1 exited with code 0

I believe this has to do with running the create-react-app development server without an interactive shell. For instance, setting:

    stdin_open: true
    tty: true

in the docker-compose.yml file works. Based on the discussion here: facebook/create-react-app#8688 it appears that the preferred solution is to set the environment variable CI=true to tell react-scripts to not expect an interactive session.

@arel
Copy link
Contributor Author

arel commented May 9, 2020

Fixed by #61

@arel arel closed this as completed May 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant