UI container does not start

[brian-lc]

Expected Behavior

UI container comes up with make start

Actual Behavior

UI container exits

Steps to Reproduce the Problem

1. Clone the repo, latest master branch
2. cd baseline and make && make deploy-contracts
3. make start
4. cd radish34 and docker-compose logs -f ui and you'll see the error (included below).

Specifications

• Version:

➜  radish34 git:(master) npm --version
6.7.0
➜  radish34 git:(master) node --version
v11.15.0
➜  radish34 git:(master) docker --version
Docker version 19.03.8, build afacb8b

• Platform:

➜  radish34 git:(master) sw_vers
ProductName:	Mac OS X
ProductVersion:	10.15.4
BuildVersion:	19E266

• Subsystem: N/A

Logs

➜  radish34 git:(master) docker-compose logs -f ui
Attaching to radish34_ui_1
ui_1                   | 
ui_1                   | > radish34-ui@1.0.0 start /app
ui_1                   | > react-scripts start
ui_1                   | 
ui_1                   | 
ui_1                   | There might be a problem with the project dependency tree.
ui_1                   | It is likely not a bug in Create React App, but something you need to fix locally.
ui_1                   | 
ui_1                   | The react-scripts package provided by Create React App requires a dependency:
ui_1                   | 
ui_1                   |   "jest": "24.9.0"
ui_1                   | 
ui_1                   | Don't try to install it manually: your package manager does it automatically.
ui_1                   | However, a different version of jest was detected higher up in the tree:
ui_1                   | 
ui_1                   |   /app/node_modules/jest (version: 24.8.0) 
ui_1                   | 
ui_1                   | Manually installing incompatible versions is known to cause hard-to-debug issues.
ui_1                   | 
ui_1                   | If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
ui_1                   | That will permanently disable this message but you might encounter other issues.
ui_1                   | 
ui_1                   | To fix the dependency tree, try following the steps below in the exact order:
ui_1                   | 
ui_1                   |   1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
ui_1                   |   2. Delete node_modules in your project folder.
ui_1                   |   3. Remove "jest" from dependencies and/or devDependencies in the package.json file in your project folder.
ui_1                   |   4. Run npm install or yarn, depending on the package manager you use.
ui_1                   | 
ui_1                   | In most cases, this should be enough to fix the problem.
ui_1                   | If this has not helped, there are a few other things you can try:
ui_1                   | 
ui_1                   |   5. If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
ui_1                   |      This may help because npm has known issues with package hoisting which may get resolved in future versions.
ui_1                   | 
ui_1                   |   6. Check if /app/node_modules/jest is outside your project directory.
ui_1                   |      For example, you might have accidentally installed something in your home folder.
ui_1                   | 
ui_1                   |   7. Try running npm ls jest in your project folder.
ui_1                   |      This will tell you which other package (apart from the expected react-scripts) installed jest.
ui_1                   | 
ui_1                   | If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
ui_1                   | That would permanently disable this preflight check in case you want to proceed anyway.
ui_1                   | 
ui_1                   | P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!
ui_1                   | 
ui_1                   | npm ERR! code ELIFECYCLE
ui_1                   | npm ERR! errno 1
ui_1                   | npm ERR! radish34-ui@1.0.0 start: `react-scripts start`
ui_1                   | npm ERR! Exit status 1
ui_1                   | npm ERR! 
ui_1                   | npm ERR! Failed at the radish34-ui@1.0.0 start script.
ui_1                   | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
ui_1                   | 
ui_1                   | npm ERR! A complete log of this run can be found in:
ui_1                   | npm ERR!     /root/.npm/_logs/2020-03-28T00_17_26_654Z-debug.log
radish34_ui_1 exited with code 1

[kthomas]

I noticed this, will be fixed in #49