I need help, i saw the balena tutorial with the raspberry pi 3, I tried to use the balena push “myapp” command but it says Run in administrator, I tried with admin powershell and it says the same thing
PS C:\WINDOWS\system32> balena push test
You don’t have enough privileges to run this operation.
Run a new Command Prompt as administrator and try running this command again.
If this is not the case, and you’re trying to burn an SDCard, check that the write lock is not set.
Additional information may be available by setting a DEBUG=1 environment
variable: “set DEBUG=1” on a Windows command prompt, or “export DEBUG=1”
on Linux or macOS.
Hi,
Would it be possible to set the DEBUG flag to find more information about this error? Balena push should not require elevated privileges it should just work.
Kind regards,
Theodor
Thanks for the reply, now it says that with set debug=1
C:\WINDOWS\system32>balena push test
Debug: original argv0=“C:\Program Files\balena-cli\bin\…\client\bin\node.exe” argv=[C:\Program Files\balena-cli\client\bin\node.exe,C:\Program Files\balena-cli\client\bin\run,push,test] length=4
[debug] Using . as build source
Error: EPERM: operation not permitted, stat ‘C:\WINDOWS\system32\LogFiles\WMI\RtBackup’
Uploading source package to balena cloud[debug] received HTTP 200 OK
[debug] handling message: {“type”:“metadata”,“resource”:“buildLogId”,“value”:956558}
[debug] handling message: {“message”:"\u001b[36m[Info]\u001b[39m Starting build for test, user g_s35400"}
[Info] Starting build for test, user g_s35400
[debug] handling message: {“message”:"\u001b[36m[Info]\u001b[39m Dashboard link: https://dashboard.balena-cloud.com/apps/1477584/devices"}
[Info] Dashboard link: https://dashboard.balena-cloud.com/apps/1477584/devices
[debug] handling message: {“message”:"\u001b[31m[Error]\u001b[39m Could not detect project type: Resolution could not be performed",“isError”:true}
[Error] Could not detect project type: Resolution could not be performed
[debug] handling message: {“message”:"\u001b[31m[Error]\u001b[39m Not deploying release.",“isError”:true}
[Error] Not deploying release.
RemoteBuildFailedError: Remote build failed
at Bluebird.then (C:\Program Files\balena-cli\client\build\utils\remote-build.js:53:19)
at tryCatcher (C:\Program Files\balena-cli\client\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Program Files\balena-cli\client\node_modules\bluebird\js\release\promise.js:517:31)
at Promise._settlePromise (C:\Program Files\balena-cli\client\node_modules\bluebird\js\release\promise.js:574:18)
at Promise._settlePromise0 (C:\Program Files\balena-cli\client\node_modules\bluebird\js\release\promise.js:619:10)
at Promise._settlePromises (C:\Program Files\balena-cli\client\node_modules\bluebird\js\release\promise.js:699:18)
at _drainQueueStep (C:\Program Files\balena-cli\client\node_modules\bluebird\js\release\async.js:138:12)
at _drainQueue (C:\Program Files\balena-cli\client\node_modules\bluebird\js\release\async.js:131:9)
at Async._drainQueues (C:\Program Files\balena-cli\client\node_modules\bluebird\js\release\async.js:147:5)
at Immediate.Async.drainQueues [as _onImmediate] (C:\Program Files\balena-cli\client\node_modules\bluebird\js\release\async.js:17:14)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
at process.topLevelDomainCallback (domain.js:126:23)