Qewd README instructions didn't work for me

27 views
Skip to first unread message

Noel da Costa

unread,
Feb 16, 2024, 4:37:00 PMFeb 16
to Enterprise Web Developer Community
Hi Rob,

The installation instructions didn't work for me. I'm on a MacBook M1. I get these errors:

% docker run -it --name qewdup --rm -p 3000:8080 -v ~/testQewd:/opt/qewd/mapped rtweed/qewd-server
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

> qewd-...@2.48.0 start /opt/qewd
> NODE_PATH=/opt/qewd/mapped/modules node qewd.js

internal/modules/cjs/loader.js:883
  throw err;
  ^

Error: Cannot find module '/opt/qewd/mapped/startup'
Require stack:
- /opt/qewd/qewd.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
    at Function.Module._load (internal/modules/cjs/loader.js:725:27)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/opt/qewd/qewd.js:103:13)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/opt/qewd/qewd.js' ]
}

Cheers,
Noel

Noel da Costa

unread,
Feb 16, 2024, 4:57:11 PMFeb 16
to Enterprise Web Developer Community
I switched to `docker pull rtweed/qewd-server-arm64`, which gets rid of the platform issue, but the other problem remains, which is that it seems to be expecting to find something on my computer at /opt/qewd/mapped. I'm confused by that because I believe the point of the docker version is that it is self-contained. Any clues?

Noel da Costa

unread,
Feb 16, 2024, 5:09:22 PMFeb 16
to Enterprise Web Developer Community
Agh... never mind. I was being overly literal with the docker command and it was pointing at the wrong folder. It's working.
Reply all
Reply to author
Forward
0 new messages