Skip to content

Conversation

@skluthe
Copy link

@skluthe skluthe commented Apr 15, 2021

Currently having an issue running the container:

calendoso_1  | internal/modules/cjs/loader.js:883
calendoso_1  |   throw err;
calendoso_1  |   ^
calendoso_1  | 
calendoso_1  | Error: Cannot find module '/root/.npm/_npx/240/lib/node_modules/prisma/scripts/preinstall-entry.js'
calendoso_1  |     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
calendoso_1  |     at Function.Module._load (internal/modules/cjs/loader.js:725:27)
calendoso_1  |     at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
calendoso_1  |     at internal/main/run_main_module.js:17:47 {
calendoso_1  |   code: 'MODULE_NOT_FOUND',
calendoso_1  |   requireStack: []
calendoso_1  | }
calendoso_1  | npm ERR! code ELIFECYCLE
calendoso_1  | npm ERR! errno 1
calendoso_1  | npm ERR! [email protected] preinstall: `node scripts/preinstall-entry.js`
calendoso_1  | npm ERR! Exit status 1
calendoso_1  | npm ERR! 
calendoso_1  | npm ERR! Failed at the [email protected] preinstall script.
calendoso_1  | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
calendoso_1  | 
calendoso_1  | npm ERR! A complete log of this run can be found in:
calendoso_1  | npm ERR!     /root/.npm/_logs/2021-04-15T15_49_11_857Z-debug.log
calendoso_1  | Install for [ 'prisma@latest' ] failed with code 1

But other than that it should be pretty good. The workflows require you to add a PAT with the packages scope from github and also a dockerhub username and password to the secrets for this repo.

It'll automatically build for multiarch (arm, x86, etc) and push to ghcr.io and dockerhub. I also added a docker-compose.yml for testing.

If you have any questions, a solution for the error above, or any requests to change this PR, feel free to let me know. Most of it was copied from https://github.com/selfhostedpro/yacht if you're curious about how any of this works that may give you some insight.

@vercel
Copy link

vercel bot commented Apr 15, 2021

@skluthe is attempting to deploy a commit to the calendso Team on Vercel.

A member of the Team first needs to authorize it.

@skluthe skluthe mentioned this pull request Apr 15, 2021
@skluthe
Copy link
Author

skluthe commented Apr 15, 2021

Didn't see #7 sorry about that! May be some useful stuff from this to copy over.

@fabioelia
Copy link

@skluthe ran into a similar issue, it looks like the postinstall https://github.com/calendso/calendso/blob/main/package.json#L9 script isn't running. I had to run yarn postinstall manually before the primsa command in order for it to run

@pumfleet
Copy link
Contributor

Going to close this PR as we're not officially supporting Docker. We may reconsider supporting it in future. Thanks very much for your help though!

@pumfleet pumfleet closed this Jun 22, 2021
@PeerRich
Copy link
Member

PeerRich commented Jul 3, 2021

docker support now exists here: https://github.com/calendso/calendso-docker powered by the community. not officially maintained by the calendso core team, yet.

KATT added a commit that referenced this pull request Sep 3, 2021
Arjun3492 referenced this pull request in onehashai/Cal-ID Sep 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants