Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker Hubにある2023.12.1のDockerイメージが Error: Cannot find package で起動できない #12823

Closed
1 task
onodai145 opened this issue Dec 27, 2023 · 2 comments
Labels
⚠️bug? This might be a bug

Comments

@onodai145
Copy link

💡 Summary

タイトルの通り、Docker Hubにある2023.12.1のDockerイメージが Error: Cannot find package '/misskey/packages/backend/node_modules/misskey-js/package.json' imported from /misskey/packages/backend/built/server/oauth/OAuth2ProviderService.js とエラーを吐き起動できません

🥰 Expected Behavior

正しく起動できる

🤬 Actual Behavior

次のエラーを吐いて起動しない

> misskey@2023.12.1 migrateandstart /misskey
> pnpm migrate && pnpm start
> misskey@2023.12.1 migrate /misskey
> cd packages/backend && pnpm migrate
> backend@ migrate /misskey/packages/backend
> pnpm typeorm migration:run -d ormconfig.js
query: SELECT * FROM current_schema()
query: SELECT version();
query: SELECT * FROM "information_schema"."tables" WHERE "table_schema" = 'public' AND "table_name" = 'migrations'
query: SELECT * FROM "migrations" "migrations" ORDER BY "id" DESC
No migrations are pending
> misskey@2023.12.1 start /misskey
> pnpm check:connect && cd packages/backend && node ./built/boot/entry.js
> misskey@2023.12.1 check:connect /misskey
> cd packages/backend && pnpm check:connect
> backend@ check:connect /misskey/packages/backend
> node ./check_connect.js
node:internal/modules/esm/resolve:205
  const resolvedOption = FSLegacyMainResolve(packageJsonUrlString, packageConfig.main, baseStringified);
                         ^
Error: Cannot find package '/misskey/packages/backend/node_modules/misskey-js/package.json' imported from /misskey/packages/backend/built/server/oauth/OAuth2ProviderService.js
    at legacyMainResolve (node:internal/modules/esm/resolve:205:26)
    at packageResolve (node:internal/modules/esm/resolve:831:14)
    at moduleResolve (node:internal/modules/esm/resolve:901:20)
    at defaultResolve (node:internal/modules/esm/resolve:1121:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:396:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:365:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:240:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:85:39)
    at link (node:internal/modules/esm/module_job:84:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}
Node.js v20.10.0
 ELIFECYCLE  Command failed with exit code 1.
 ELIFECYCLE  Command failed with exit code 1.

📝 Steps to Reproduce

No response

💻 Frontend Environment

* Model and OS of the device(s):
* Browser:
* Server URL:
* Misskey:

🛰 Backend Environment (for server admin)

* Installation Method or Hosting Service: Docker
* Misskey: 2023.12.1
* Node: 20.10.0
* PostgreSQL: 15.1
* Redis: 7.0.10
* OS and Architecture: Debian GNU/Linux 10 x86_64

Do you want to address this bug yourself?

  • Yes, I will patch the bug myself and send a pull request
@onodai145 onodai145 added the ⚠️bug? This might be a bug label Dec 27, 2023
@WinLinux1028
Copy link

#12822 と重複しているのでこちらへどうぞ

@anatawa12
Copy link
Member

Duplicate of #12822

@anatawa12 anatawa12 marked this as a duplicate of #12822 Dec 27, 2023
@anatawa12 anatawa12 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⚠️bug? This might be a bug
Projects
None yet
Development

No branches or pull requests

3 participants