Attempting to add spotify skill crashes almond container.

[gangrif]

I tried to add the Spotify skill to my almond container today.

After clicking through the skills UI to add the spotify skill, after being directed through the oauth on dev.stanford.edu, and redirecting back to my local instance of almond, I get an error in my browser that I cannot connect.

Checking podman, I see that the almond container is down, and the logs read:

GET /devices/create 200 41.498 ms - 3176
GET /stylesheets/bootstrap.min.css 304 5.976 ms - -
GET /stylesheets/style.css 304 5.549 ms - -
GET /javascripts/validator.min.js 304 5.296 ms - -
GET /javascripts/jstz.min.js 304 4.884 ms - -
GET /javascripts/shared.js 304 2.380 ms - -
GET /javascripts/devices-create.js 304 1.168 ms - -
GET /devices/oauth2/com.spotify 302 1.351 ms - 238
Loaded class definition for com.spotify, module type: org.thingpedia.v2, version: 46
/opt/almond/main.js:24
process.on('unhandledRejection', (up) => { throw up; });
^

Error: failed to retrieve spotifyd binary package: Error: spawn wget ENOENT
at SpotifyDaemon._download (/var/lib/almond-server/cache/device-classes/com.spotify/spotifyd.js:131:19)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! almond-server@2.0.0-beta.1 start: node main.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the almond-server@2.0.0-beta.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/almond/.npm/_logs/2021-05-12T13_26_31_739Z-debug.log

The contents of the referenced debug log is:

[root@cd8f7bcd0d50 almond]# cat /home/almond/.npm/_logs/2021-05-12T13_26_31_739Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@6.14.12
3 info using node@v12.22.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle almond-server@2.0.0-beta.1prestart: almond-server@2.0.0-beta.1
6 info lifecycle almond-server@2.0.0-beta.1start: almond-server@2.0.0-beta.1
7 verbose lifecycle almond-server@2.0.0-beta.1start: unsafe-perm in lifecycle true
8 verbose lifecycle almond-server@2.0.0-beta.1start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/opt/almond/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle almond-server@2.0.0-beta.1start: CWD: /opt/almond
10 silly lifecycle almond-server@2.0.0-beta.1start: Args: [ '-c', 'node main.js' ]
11 silly lifecycle almond-server@2.0.0-beta.1start: Returned: code: 1 signal: null
12 info lifecycle almond-server@2.0.0-beta.1start: Failed to exec start script
13 verbose stack Error: almond-server@2.0.0-beta.1 start: node main.js
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:314:20)
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:314:20)
13 verbose stack at maybeClose (internal/child_process.js:1022:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid almond-server@2.0.0-beta.1
15 verbose cwd /opt/almond
16 verbose Linux 5.11.14-200.fc33.x86_64
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v12.22.1
19 verbose npm v6.14.12
20 error code ELIFECYCLE
21 error errno 1
22 error almond-server@2.0.0-beta.1 start: node main.js
22 error Exit status 1
23 error Failed at the almond-server@2.0.0-beta.1 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]