atlas2
atlas2 copied to clipboard
LeadingEdgeForum
docker-compose up fails
Currently with a fresh checkout running docker-compose up will fail on the npm step.
Step 5/6 : RUN npm install --quiet
---> Running in 0d16a75a6eb2
npm WARN deprecated [email protected]: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
npm WARN deprecated [email protected]: Please see v6.X+ at https://www.npmjs.com/org/sendgrid
npm WARN deprecated [email protected]: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: Package no longer supported. Contact [email protected] for more info.
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm ERR! code ETARGET
npm ERR! notarget No matching version found for [email protected]
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'Atlas2'
npm ERR! notarget
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-07-18T11_51_01_769Z-debug.log
ERROR: Service 'web' failed to build: The command '/bin/sh -c npm install --quiet' returned a non-zero code: 1
I just had that happen too. If you get a reply how to fix this would you be kind enough to let me know too? :-)
ME again. Its a version of [email protected] that is wrong. The latest is 2.1.1. This implies the developer had early access to a newer version :-) So we gotta go check out [email protected] is hiding... any ideas
I'm travelling at the moment. What you may want to do is to switch to the branch https://github.com/LeadingEdgeForum/atlas2/tree/v2-service-branch and try to run docker there.
Master contains some work in progress.
All cool. I’ll have another go and let you know.
Best Regards Mladen
Sent from M's iPhone. I blame my phone for any spelling mistakes
On 25 Jul 2018, at 21:31, Chris [email protected] wrote:
I'm travelling at the moment. What you may want to do is to switch to the branch https://github.com/LeadingEdgeForum/atlas2/tree/v2-service-branch and try to run docker there.
Master contains some work in progress.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
@mmatijas if you open the package.json file you can change "socket.io-client": "2.1.4" to "socket.io-client": "2.1.1" that fixed it for me.
@leigit @mmatijas please be adviced that master is some unfinished work in progress. It will not work. Following command list got me the tool running:
git clone https://github.com/LeadingEdgeForum/atlas2.git
cd atlas2/
git checkout v2-service-branch
docker-compose up
However, I managed to reproduce the issue after updating Docker deamon to 18.06 and trying to build from master immediately. After resetting docker (removing all data), the new build from the v2-service-branch worked fine.
I suspect this is a problem with cached docker images, but I do not have sufficient command of docker to propose anything beyond docker reset (Docker icon -> Preferences -> Reset -> Reset disk image).