EACCESS with npm install -g firebase-tools
#25325
-
Started happening few mins ago, reported it to @w9jds but suspecting something changed on github’s docker. Below is a copy of details mentioned at w9jds/firebase-action#46 (comment)
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
Facing the same issue all of a sudden. Unable to deploy anything. |
Beta Was this translation helpful? Give feedback.
-
This was actually caused by Note, it was reproducible with a local version of docker as well. |
Beta Was this translation helpful? Give feedback.
-
w9jds:
I can confirm v1.4.0 worked for me. Thanks for the quick update! :slight_smile: Edit: I tried |
Beta Was this translation helpful? Give feedback.
-
@anandchakru The owner of that action (w9jds) has resolved this issue. Does v1.4.0 or master version work for you? Kindly let me know your result. |
Beta Was this translation helpful? Give feedback.
-
try using the --unsafe-perm flag |
Beta Was this translation helpful? Give feedback.
This was actually caused by
firebase-tools
due to how docker works (It pulls and installs latest tool version each time it runs) it pulled a bad version, there are issues opened to fix it. However, I have pushed v1.4.0 which addresses the issue and uses a workaround to get it to work. If you are pointing to master, the build should just work now if you re-run it. Otherwise, point your action to the latest release and you should be good.Note, it was reproducible with a local version of docker as well.