Fedora Silverblue - aiming to build API with npm & node.js - script won't run on Silverblue even tho actually running from Ubuntu VM

Ask Fedora
,
1

I’m trying to go through a course that explains how to build an API.
I’m running Fedora Silverblue as the main OS on a Thinkpad and an Ubuntu Gnome Boxes VM.
I’m getting an error and I believe that this is because the script executes everything from “/usr/share/npm/…” and with Silverblue everything is seemingly rooted (if that’s what it’s called) in the “var” directory and containerized thereon after.
I’m not comfortable enough with containers to use Podman or Skopeo or Buildah etc. I’ve noticed that the Ubuntu VM won’t work:
a.) When I download something on it and try to run it after. I need to restart the whole computer since Fedora Silverblue is the main OS;
b.) When downloading things like VS Codium - where I would need to add libraries.
VS Codium, for the record, needs an update but seemingly, the scripts that come with this software and what’s in Silverblue don’t line up since everything is based out fo “var” in Silverblue.
I’m not quite sure how to resolve these issue. Any help?
Few bits of the error:

/.npm/orders_project_starting
10 silly lifecycle orders-project@1.0.0~start: Args: [ '-c', 'node server.js' ]
11 silly lifecycle orders-project@1.0.0~start: Returned: code: 1  signal: null
12 info lifecycle orders-project@1.0.0~start: Failed to exec start script
13 verbose stack Error: orders-project@1.0.0 start: `node server.js`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:198:13)
13 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:198:13)
13 verbose stack     at maybeClose (internal/child_process.js:982:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid orders-project@1.0.0

16 verbose Linux 5.11.0-41-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v10.19.0
19 verbose npm  v6.14.4
20 error code ELIFECYCLE
21 error errno 1
22 error orders-project@1.0.0 start: `node server.js`
22 error Exit status 1
23 error Failed at the orders-project@1.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
2

Are you saying that when you download software in your Ubuntu VM, you need to restart the Silverblue Host? If so, I think your problem is actually somewhere else. The software on the VM should never require changes on the host. VMs don’t work like that.

Are you installing VSCodium on the host or the VM? If you are installing it on the host, use the flatpak. If you are installing it in the VM, it doesn’t matter how the host treats the filesystem. The VM has it’s own completely separate filesystem and doesn’t know anything about the filesystem on the host.

That looks like an error from inside the Ubuntu VM. You should ask for support through the Ubuntu support channels. It has nothing to do with the fact that your host is Silverblue.

2 Likes
3

I’ve installed VSCodium on both and tested on both - the copy/pasted code might’ve been form Ubuntu and that’s because the scripts won’t run on Silverblue. There was also a security issue with the Flatpak when I installed VSCodium and they said not* to download the flatpak at that point - so perhaps I’ll give it another go.
I was under the impression that since it’s Silverblue and not just a regular Fedora Gnome Boxes vm situation that there’d be some conflict there as I remember coming across a forum that talked about that, but I’ll submit that you know much more than I so I’ll figure this out on the Ubuntu forums. Thanks for your response.