Now i’m able to run the command/service on my machine (amd64 Ubuntu 16.04 LTS) with Node.js v12.2.0 installed but i cant find the node.js env not in multipass instance not in another machine with installed Ubuntu Core 18, i mean i can’t run command as node --version and so on and even the snap app doesn’t work neither command neither service.
My questions are :
1 - my-snap-file.snap bundle the Node.js v12.3.1 inside the mysnap ?
2 - how i can test the node.js is working with the right version in multipass and other machine where i’ve installed only the snap bundling node.js ?
OK … i’ve already try this but does’t work on ubuntu core only … so i’m searching a method to debug the node.js environment into multipass and ubunto core when snap is installed …
I’ve opened this on stackoverflow too
Hi ogra … i’m trying to follow that route but with a snap that working on different Ubuntu LTS versions i cannot get it works on Ubuntu Core 18 on RaspBerry Pi3 ! Seems it cannot run due to error in handle the node exec in snap environment… So my first problem is looking in the Ubuntu Core snap folder :
/snap//bin
when i’m try to running ./node or ./node --version or sudo ./node i get the error :
-bash: ./node: cannot execute binary file: Exec format error
this sounds like your snap was not built on the actual target architecture you want to run it on … make sure you build armhf snaps actually on an armhf device …
here you tell snapcraft that building on amd64 produces binary snaps that can run on amd64 and armhf … which is indeed not true (since building on amd64 will pull in only amd64 binaries). i’d drop that statement completely and make sure to build the armhf version on an armhf device (or on build.snapcraft.io).