You are attempting to run Meteor as the "root" user

[rclai]

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:

You have run Meteor as root. Your permissions in your app directory will be incorrect if you ever attempt to perform any Meteor tasks
as your non-root user. You probably didn't want this, but you can fix it by running the following from the root of your project:

sudo chown -Rh <username> .meteor/local

--unsafe-perm: unknown option.                
Usage: meteor run [target..] [options]

Searches upward from the current directory for the root directory of a
Meteor project, then runs that project in local development
mode. You can use the application by pointing your web browser at
localhost:3000. No internet connection is required.

Whenever you change any of the application's source files, the changes
are automatically detected and applied to the running application.

The application's database persists between runs. It's stored under
the .meteor directory in the root of the project.

If you have added a platform to your app with 'meteor add-platform', you can
pass one of the following targets as an argument to this command.

Targets:
  android          Run on the Android emulator.
  android-device   Run on a connected Android device.
  ios              Run on the iOS simulator.
  ios-device       Open Xcode with the iOS project for this app, where you can
                   run your app on a connected iOS device.

Options:
  --port, -p       Port to listen on (instead of the default 3000). Also
                   uses port N+1 and a port specified by --app-port.
                   Specify as --port=host:port to bind to a specific interface.
  --debug-port     Specify a port to enable server-side debugging. The
                   server will be paused at startup, waiting for incoming
                   connections from debugger clients on the specified port.
  --mobile-server  Location where mobile builds connect to the Meteor server.
                   Defaults to your local IP and the port that the Meteor
                   server binds to. Can include a URL scheme (for
                   example, --mobile-server=https://example.com:443).
  --production     Simulate production mode. Minify and bundle CSS and JS files.
  --raw-logs       Run without parsing logs from stdout and stderr.
  --settings       Set optional data for Meteor.settings on the server.
  --release        Specify the release of Meteor to use.
  --verbose        Print all output from builds logs.
  --no-lint        Don't run linters used by the app on every rebuild.
  --allow-incompatible-update   Allow packages in your project to be upgraded or
                   downgraded to versions that are potentially incompatible with
                   the current versions, if required to satisfy all package
                   version constraints.
  --test           [Experimental] Run Velocity tests using phantomjs and exit.

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.

[rclai]

Reinstalling did not fix the issue.

Meteor is still not recognizing the --unsafe-perm still for Meteor apps on older versions (I have not tested on newest versions).

[jpmelnik]

+1 Same for me. I'm over Ubuntu 16.04 and I can't run "meteor update".

You are attempting to run Meteor as the "root" user. If you are developing, this is almost certainly not what you want to do and will likely result in incorrect file permissions. However, if you are
running this in a build process (CI, etc.) or you are absolutely sure you know what you are doing, add the --unsafe-perm flag to this command to proceed.

[benjamn]

Commented on the PR: #7821 (comment)

[ismail-syed]

Same here!
Any suggestions?

It was working fine earlier this morning. I just happened to notice this about an hour ago.

>sudo meteor

You are attempting to run Meteor as the "root" user. If you are developing, this is almost certainly *not* what you want to do and will likely result in incorrect file permissions. However, if you are running this in a build process (CI,
etc.) or you are absolutely sure you know what you are doing, add the `--unsafe-perm` flag to this command to proceed.

I usually have to run with sudo, if not I get the following.

>meteor
[[[[[ ~/Development/project ]]]]]

=> Started proxy.
=> Started MongoDB.

/Users/iSyed/.meteor/packages/ecmascript/.0.4.6.pxweny++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:165
      throw error;
            ^
Error: EACCES, open '/Users/iSyed/.meteorsession' 

[jpmelnik]

1. I removed meteor completly from my system.
2. I did a backup for my project.
3. I removed the project
4. Install meteor again.
5. I created new meteor project without root.
6. I imported the project from the backup.
7. Now, meteor / meteor run / meteor update works as expected.

[jpmelnik]

Update #1:

The package momentjs:moment@2.15.2 stop the app execution.

Update #2

momentjs:moment, added version 2.8.4, works fine.

[jay-depot]

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.

[abernix]

@isyed867 Your situation is one of the (many) problems that this --unsafe-perm argument is trying to solve. In development, on your machine, where you have multiple accounts, you should not run Meteor as root (i.e. with sudo) as it will break a variety of things. To fix your problem, you should be able to run sudo rm ~/.meteorsession and then run meteor login again without sudo.

[abernix]

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 root user, but it has had its drawbacks and a common security recommendation is to NOT do this. See the USER setting in the Dockerfile reference and Dockerfile best practices. There is really very little reason to run meteor as root, even in Docker.

That being said, this is indeed an unintended bug affecting folks who run pre-Meteor 1.4.2 apps as root (even with the --unsafe-perm flag). For the explanation as to why, see my comment here: #7821 (comment).

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 meteor-tool. But! Be absolutely sure that you update this version, or remove this workaround as you update Meteor versions.

I'll try to take a look at this today.