All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9531] NPM fails to build embedded modules
Date: Sun, 05 Mar 2017 15:34:52 +0000	[thread overview]
Message-ID: <bug-9531-163-Z4u4yNblFP@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9531-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9531

--- Comment #13 from Martin <martin@barkynet.com> ---
I tested this and setting BR2_PACKAGE_NODEJS_MODULES_ADDITIONAL="ghost at 0.11.3"
builds fine when building as a non-root user.

What is happening here is npm is dropping it's root privileges before running
node-pre-gyp which is why you see "node-pre-gyp: Permission denied" because it
can't access the files under /root.  --unsafe-perm stops this behaviour which
is why it then works.

I agree with Peter, building as root should be avoided.  I would recommend you
modify your Dockerfile to build as a non-root user.

The one change which might be worth making is a recommendation against building
as root in the manual and/or the Makefile.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2017-03-05 15:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29 10:59 [Buildroot] [Bug 9531] New: NPM fails to build embedded modules bugzilla at busybox.net
2016-12-29 11:10 ` [Buildroot] [Bug 9531] " bugzilla at busybox.net
2016-12-29 13:26 ` bugzilla at busybox.net
2016-12-29 13:33 ` bugzilla at busybox.net
2016-12-29 23:50 ` bugzilla at busybox.net
2016-12-30 19:43 ` bugzilla at busybox.net
2016-12-31  2:31 ` bugzilla at busybox.net
2016-12-31 11:39 ` bugzilla at busybox.net
2016-12-31 11:54 ` bugzilla at busybox.net
2016-12-31 11:58 ` bugzilla at busybox.net
2016-12-31 14:19 ` bugzilla at busybox.net
2016-12-31 14:23 ` bugzilla at busybox.net
2016-12-31 15:42 ` bugzilla at busybox.net
2017-03-05 15:34 ` bugzilla at busybox.net [this message]
2017-03-05 15:38 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-9531-163-Z4u4yNblFP@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.