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
You are attempting to run Meteor as the "root" user #7959
Comments
Reinstalling did not fix the issue. Meteor is still not recognizing the |
+1 Same for me. I'm over Ubuntu 16.04 and I can't run "meteor update".
|
Commented on the PR: #7821 (comment) |
Same here! It was working fine earlier this morning. I just happened to notice this about an hour ago.
I usually have to run with sudo, if not I get the following.
|
|
I think #7964 is the same issue. This is kind of a big deal, as it's breaking Docker deployments for anyone not on the bleeding edge version of Meteor. |
@isyed867 Your situation is one of the (many) problems that this |
If it's not obvious by the error outputted: You can avoid this issue by not running Meteor as root which is not recommended and frequently causes problems (see above). Some environments only have one (root) user by default and I'm aware that it's common practice to run everything inside Docker as the That being said, this is indeed an unintended bug affecting folks who run pre-Meteor 1.4.2 apps as Please try this suggested workaround for the time-being – instead of the usual Meteor install command, use these: export METEOR_NO_RELEASE_CHECK=true # make sure this is set in your environment.
curl https://install.meteor.com/?release=1.4.1.3 | sh # You can use the exact version you're deploying here, or 1.4.1.3. This will also likely speed up your Docker builds if your app is using an older version of Meteor than the current official release since it will avoid double-downloading of I'll try to take a look at this today. |
Thanks, @abernix's workaround is working. |
Uh, @abernix, the error started happening again even after doing:
Did your recent commit cause that? |
I had to re-run the workaround commands again to make it work. Weird. |
My recent commit is on a different branch as a proposed fix, so no. If it just started happening again it's because the download just went on in the background – meaning either You can try also setting tl;dr if |
Ah okay. |
This is a majorly breaking change for my team. --unsafe-perm doesn't work for us, meteor processes that argument correctly, but whatever function implements
Is it possible to revert to an older version of whatever meteor wrapper changed to break this? |
Have you tried the above? |
Thought we had, tried it again now, looks like it's working. Thanks, that workaround will do. |
some one have sollition for this case? i still have this issue |
Meteor 1.4.2.1 is out now! Please run |
Testing @benjamn - |
Finally confirmed working with --allow-superuser on docker image node:latest ... |
some project work other project not work `Even with METEOR_ALLOW_SUPERUSER or --allow-superuser, permissions in your app directory will be incorrect if you sudo chown -Rh .meteor/local You are attempting to run Meteor as the "root" user. If you are developing, this is almost certainly not what you i use meteor --allow-superuser |
|
As far as I know, you implemented it downgrade compatible, so I was expecting |
@rsercano The message you are receiving is not an error – it is just a warning and Meteor should not be stopping at that point. It's very possible that it's sitting there with that message on your screen, but everything is still continuing and running in the background. |
@abernix Indeed, that's what I was expecting but after a while (like 3-5 minute after) it gives below error:
docker kills this container. But it has this flag already. Here's the docker file: |
@rsercano Ok, I understand why it is happening, but the problem is still fixed by Meteor 1.4.2.1 and while you do have the latest tool installed, your app itself is still using the buggy version. You should upgrade your actual app to Meteor 1.4.2.1 and the problem should go away. 1.4.2.1 is also a very important bug-fix release for other reasons and I would recommend doing it as soon as possible. The upgrade should be painless, but you will need to make sure that you have the Please see this blog post for more information. |
@abernix thanks it seems to be fixed after upgrading 1.4.2.1 |
this shouldn't be happening if you haven't upgraded anything. I don't want to upgrade anything. I want to keep everything exactly the same. I did not opt into this. How did this even happen. I use sudo to use port 80 on my computer. This is messed up. So that said, is there a way to like upgrade globally just the cli while not updating my app. I'm not sure about these details, and that's why what's going on here is very distressing. I'm not even confident a version-locked app and an upgraded CLI will be able to run my legacy app. |
@faceyspacey Not providing us with any information about what your situation is right now (app version, error output, etc.) is not likely to get you any help in resolving your problem and the answer as to "Why this happened" is higher up in this thread, if you care. Long story short, if you start your existing, older Meteor app with If this doesn't work, we'll be happy to help but the most important information to get to help you would be the output of |
@abernix I literally just got it to work. It wasn't that bad. Upgrading to the latest version of meteor and using ps. You may want to somehow retitle this issue with the answer, cuz every legacy app developer will waste an hour reading the issue wall. @rclai |
@faceyspacey Glad you got it to work. Hopefully you understand the reason for it based on the message – it is actually a big deal and causes a lot of very hard to debug support problems which is why it is so forcefully required. If it works for you, keep on doing what you've been doing, but you'll have to run |
After trying the suggestions above and had no success, this is what I did. I changed the content of .meteor/release to METEOR@1.4.2.1 and removed .meteor/local. Then I run meteor in the terminal and it worked like magic. Hopefully this works for you. |
meteor-tupperware has the following issue, which caused errors when building: meteor/meteor#7959 chriswessels/meteor-tupperware#27
meteor-tupperware has the following issue, which caused errors when building: meteor/meteor#7959 chriswessels/meteor-tupperware#27
meteor-tupperware has the following issue, which caused errors when building: meteor/meteor#7959 chriswessels/meteor-tupperware#27
meteor-tupperware has the following issue, which caused errors when building: meteor/meteor#7959 chriswessels/meteor-tupperware#27
Builds stopped working in docker due to this issue: meteor/meteor#7959
I used this on ubuntu 16 and it works
You can use meteor in root.Used meteor in root to build an apk on digitalocean 4GB droplet. This is the location of the generated apk
|
Again, if you MUST run as privileged |
Uh... Why is this error happening? I did not even upgrade any of my Meteor apps at all. Why would this shell flow control be getting hit when I haven't even updated to the new version? This must have come up as a result of you pushing out this latest build.
Anyway, running this:
meteor run --unsafe-perm --port 3002
Does not fix the issue, and it's because I'm running an old version of Meteor and all I get is this:
I know I shouldn't be running as root, but this just so happened to be the dev server I'm building in and don't have the flexibility to set up users on this server.
There seems to be some hijacking of the old Meteor versions in my server as a result of your update.
The text was updated successfully, but these errors were encountered: