Open twhiston opened 6 years ago
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 socket.io-client@2.1.4 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 wheresocket.io-client@2.1.4 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 notifications@github.com 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
).
Currently with a fresh checkout running
docker-compose up
will fail on the npm step.