-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception thrown with accounts-base. #79
Comments
I have something like this. I managed to fire it up without docker in production mode by installing node 10.4.X and manually reinstall fibers in bundle, but I can not make it work in docker. Its really a problem, cause I don't want to lock myself with node 10.4.X on my server |
@Aquator Node 0.10.4x is currently a requirement of Meteor. That's not optional. |
@jshimko yeah, I ended up with building a docker image from node:0.10 and do it step by step, so I can reinstall fibers and do magic... there were of course some other issues as well regarding remote mongodb, oplog, etc, so once all other issues are behind me I'll take another shot with mongod - the fact that I am new do docker also not helping :D |
It's interesting that I can run my app with meteord in my local docker virtual machine, but the container fails to run in a production vps. It gave the same error as @mlschuh described. I thought that a container should work in any machine. What might be the cause of the problem? |
Is it possible because that the production vps failed to connect to the mLab? |
I've encountered the following error message after running a new image of the meteor example simple-todos. It takes it a minute to hit this point but it always does.
When executing the app with meteor and having it connect to the remote database using the same MONGO_URL, it works without a problem.
To replicate, I simply clone the meteor github, browse into the example folder, and then follow the instructions on the readme of meteord.
Any tips on where to start digging?
-Mitch
The text was updated successfully, but these errors were encountered: