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
Step 7/16 : RUN [ -f esy.lock ] || node_modules/.bin/esy solve
---> Running in 7f69619a797f
info solve 0.6.12-dev (using esy.json)
info checking https://github.com/ocaml/opam-repository for updates...
info checking https://github.com/esy-ocaml/esy-opam-override for updates...
info resolving esy packages: done
error: error running command: '/build/node_modules/esy/3/i/esy-71a059e4/lib/esy/esySolveCudfCommand' '--strategy=-count[staleness,solution]' '--timeout=60.' '/tmp/esy-14ddec/in.cudf' '/tmp/esy-14ddec/out.cudf'
esy: exiting due to errors above
The command '/bin/sh -c [ -f esy.lock ] || node_modules/.bin/esy solve' returned a non-zero code: 1
ERROR: Service 'web' failed to build : Build failed
Possible reasons
I could not understand what was trying to be conveyed in the first command of the Deploy section $ rsync -rlv . build@my-droplet:app --exclude _esy --exclude node_modules
So I just moved over all the files found in https://github.com/aantron/dream/tree/master/example/z-docker-esy#files
Then ran bash deploy.sh
Commenting out the line from the Dockerfile just leads to an error in the next line
The text was updated successfully, but these errors were encountered:
By following the steps in https://github.com/aantron/dream/tree/master/example/z-docker-esy#files
Running bash deploy.sh fails on step 7
https://github.com/aantron/dream/tree/master/example/z-docker-esy#files
Possible reasons
I could not understand what was trying to be conveyed in the first command of the Deploy section
$ rsync -rlv . build@my-droplet:app --exclude _esy --exclude node_modules
So I just moved over all the files found in
https://github.com/aantron/dream/tree/master/example/z-docker-esy#files
Then ran bash deploy.sh
Commenting out the line from the Dockerfile just leads to an error in the next line
The text was updated successfully, but these errors were encountered: