folks - I think I've seen this before, but can't r...
# fleet
j
folks - I think I've seen this before, but can't remember the cause and my google fu's failing me at the moment. 😕 Fresh ubuntu 20.04 install with node 16 via nvm, then `npm install -g fleetctl`:
Copy code
$ fleetctl
/home/parallels/.nvm/versions/node/v16.16.0/lib/node_modules/fleetctl/install/v4.18.0/fleetctl: 1: Syntax error: "(" unexpected
z
Hmm, this isn't familiar... I'm going to try to set up a Ubuntu20.04 VM.
j
it feels like a variable expansion in a shell script isn't happening due to empty variable or something
z
if you
cat
that path is it a JS file?
Should look something like this
Copy code
cat $(which fleetctl)
#!/usr/bin/env node

const child = require("child_process");
j
Copy code
parallels@ubuntu-linux-20-04-desktop:~$ file !$
file /home/parallels/.nvm/versions/node/v16.16.0/lib/node_modules/fleetctl/install/v4.18.0/fleetctl
/home/parallels/.nvm/versions/node/v16.16.0/lib/node_modules/fleetctl/install/v4.18.0/fleetctl: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=p9aF4mSDPD7dn5oID5Sw/bnwrzY9xVNJrsCLqY0HR/XgxMWr5TOcYnYWJ52wMp/41kSRVs3rA1tnEVsMs2k, not stripped
parallels@ubuntu-linux-20-04-desktop:~$ which fleetctl
/home/parallels/.nvm/versions/node/v16.16.0/bin/fleetctl
parallels@ubuntu-linux-20-04-desktop:~$ file `!!`
file `which fleetctl`
/home/parallels/.nvm/versions/node/v16.16.0/bin/fleetctl: symbolic link to ../lib/node_modules/fleetctl/run.js
oh hm that's an x86 binary, this is an arm ubuntu VM on a mac m1...
z
Oh, we are not publishing arm64 binaries for fleetctl yet
Any reason not to just run fleetctl on the mac?
j
(sorry I shoulda mentioned arm originally) well - I'm trying to put some legwork in before I asked the channel the core question - I've got fleetctl working on the mac, trying to generate windows binaries without any luck, so I was going to try from the linux side.
z
Ah yeah we've seen it to be flakey from M1 macs. It works ~100% of the time on Intel, but probably more like 20% of the time on M1. Maybe try again a few times?