Skip to content
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 don't have enough privileges to run this operation . . ." #472

Closed
emirotin opened this issue Apr 4, 2017 · 3 comments
Closed

"You don't have enough privileges to run this operation . . ." #472

emirotin opened this issue Apr 4, 2017 · 3 comments

Comments

@emirotin
Copy link
Contributor

emirotin commented Apr 4, 2017

The user on OSX 10.10 has this error when running device init. It happens after the password warning (but the prompt is not shown so the user is probably having passwordless sudo) so it's related to the os init command that involves writing the image.

You don't have enough privileges to run this operation.
Try running this command again prefixing it with sudo.

If this is not the case, and you're trying to burn an SDCard, check that the write lock is not set.

If you need help, don't hesitate in contacting us at:

GitHub: https://github.com/resin-io/resin-cli/issues/new
Forums: https://forums.resin.io

You can safely remove /dev/disk2 now
Done

This means EPERM / EACCESS error is thrown from the resin internal osinit command

Front logo Front conversations

@emirotin emirotin changed the title "You don't have enough privilages to run this operation . . ." "You don't have enough privileges to run this operation . . ." Apr 4, 2017
@emirotin
Copy link
Contributor Author

emirotin commented Apr 4, 2017

As the very minimum if the spawned sudo command fails we should crash the main command, seems not to be the case right now.

We should also pass down the DEBUG flag to the spawned commands (how do we do it cross-platform?)

@pdcastro
Copy link
Contributor

Related to #385

@pdcastro
Copy link
Contributor

Closed in favour of #1722.

@pdcastro pdcastro removed this from the Ordered Backlog milestone Apr 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants