starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-03-01 11:21:46 +03:00
Code Issues 396 Packages Projects Releases 16 Wiki Activity

[Bug]: Segmentation fault - in DEV Setup #824

New Issue
Open
opened 2026-02-04 21:25:17 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 21:25:17 +03:00
Owner
Copy Link

Originally created by @knom on GitHub (Sep 26, 2025).

Where is the problem occurring?

I'm not sure

What browsers are you seeing the problem on?

Other

Current behavior

I'm running the docker setup of the DEV environment, according to:
https://docs.planka.cloud/docs/development/set-up-environment/

Desired behavior

No response

Steps to reproduce

Upon running docker-compose -f docker-compose-dev.yml up

I get the following error:

planka-server_1 | bash: line 1: 47 Segmentation fault (core dumped) npm run db:init

I'm using the default user settings in the .env file:

DEFAULT_ADMIN_EMAIL=demo@demo.demo DEFAULT_ADMIN_PASSWORD=demo DEFAULT_ADMIN_NAME=Demo Demo DEFAULT_ADMIN_USERNAME=demo

I have identified, issue is related to create-admin-user.js

Other information

No response

Originally created by @knom on GitHub (Sep 26, 2025). ### Where is the problem occurring? I'm not sure ### What browsers are you seeing the problem on? Other ### Current behavior I'm running the docker setup of the DEV environment, according to: https://docs.planka.cloud/docs/development/set-up-environment/ ### Desired behavior _No response_ ### Steps to reproduce Upon running ``docker-compose -f docker-compose-dev.yml up`` I get the following error: ``planka-server_1 | bash: line 1: 47 Segmentation fault (core dumped) npm run db:init`` I'm using the default user settings in the .env file: `` DEFAULT_ADMIN_EMAIL=demo@demo.demo DEFAULT_ADMIN_PASSWORD=demo DEFAULT_ADMIN_NAME=Demo Demo DEFAULT_ADMIN_USERNAME=demo `` I have identified, issue is related to ``create-admin-user.js`` ### Other information _No response_
OVERLORD commented 2026-02-04 21:25:23 +03:00
Author
Owner
Copy Link

@StevenJCorreia commented on GitHub (Sep 27, 2025):

I'm having the same issue.

Update:

I have a quick fix for now if anyone needs. This simply swaps the image for 22.20.0-slim.

segfault-fix.patch

@StevenJCorreia commented on GitHub (Sep 27, 2025): I'm having the same issue. Update: I have a quick fix for now if anyone needs. This simply swaps the image for `22.20.0-slim`. [segfault-fix.patch](https://github.com/user-attachments/files/22575488/segfault-fix.patch)
OVERLORD commented 2026-02-04 21:25:28 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Sep 28, 2025):

Hey! Thanks for reporting this.

I just tested the dev compose environment on Mac, and everything works fine for me (in the end). The only issue I ran into the first time was errors caused by existing node_modules and server/.venv from my local Node.js and Python installs - the binaries there didn't match the versions installed in the image.

My guess is you might be running into the same issue if you've already run npm i locally. You can try removing the conflicting folders by:

rm -rf node_modules client/node_modules server/node_modules server/.venv

Then try running the dev compose again. If that doesn't solve the issue, it'll definitely be interesting to investigate further...

I'm having the same issue.

Update:

I have a quick fix for now if anyone needs. This simply swaps the image for 22.20.0-slim.

segfault-fix.patch

Thanks for the update! Could you please confirm whether the previous version with node:22-alpine still fails even after removing all the node_modules and server/.venv folders?

@meltyshev commented on GitHub (Sep 28, 2025): Hey! Thanks for reporting this. I just tested the dev compose environment on Mac, and everything works fine for me (in the end). The only issue I ran into the first time was errors caused by existing `node_modules` and `server/.venv` from my local Node.js and Python installs - the binaries there didn't match the versions installed in the image. My guess is you might be running into the same issue if you've already run `npm i` locally. You can try removing the conflicting folders by: ``` rm -rf node_modules client/node_modules server/node_modules server/.venv ``` Then try running the dev compose again. If that doesn't solve the issue, it'll definitely be interesting to investigate further... > I'm having the same issue. > > Update: > > I have a quick fix for now if anyone needs. This simply swaps the image for `22.20.0-slim`. > > [segfault-fix.patch](https://github.com/user-attachments/files/22575488/segfault-fix.patch) Thanks for the update! Could you please confirm whether the previous version with `node:22-alpine` still fails even after removing all the `node_modules` and `server/.venv` folders?
OVERLORD commented 2026-02-04 21:25:37 +03:00
Author
Owner
Copy Link

@StevenJCorreia commented on GitHub (Sep 28, 2025):

Thanks for the update! Could you please confirm whether the previous version with node:22-alpine still fails even after removing all the node_modules and server/.venv folders?

No problem!

After doing the following:

  • Stashed my changes
  • Removed all node_modules and .venv directories as listed above
  • Nuked docker as a precaution

I spun up the dev compose file and followed the logs to see that the segfault is no longer an issue!

Image

Sorry for the confusion, looks like I tried dev locally and switched to docker half-way through. Thanks for your help!

Also, should this information go in a disclaimer somewhere in the contributing documentation?

@StevenJCorreia commented on GitHub (Sep 28, 2025): > Thanks for the update! Could you please confirm whether the previous version with `node:22-alpine` still fails even after removing all the `node_modules` and `server/.venv` folders? No problem! After doing the following: - Stashed my changes - Removed all `node_modules` and `.venv` directories as listed above - Nuked docker as a precaution I spun up the dev compose file and followed the logs to see that the segfault is **no longer** an issue! <img width="297" height="105" alt="Image" src="https://github.com/user-attachments/assets/598f93f9-6a27-4ea8-96b1-f4c79b97a6cb" /> Sorry for the confusion, looks like I tried dev locally and switched to docker half-way through. Thanks for your help! Also, should this information go in a disclaimer somewhere in the contributing documentation?
OVERLORD commented 2026-02-04 21:25:42 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Sep 30, 2025):

Thanks for testing! Yep, definitely need to add this disclaimer to the docs, will do it right away.

@meltyshev commented on GitHub (Sep 30, 2025): Thanks for testing! Yep, definitely need to add this disclaimer to the docs, will do it right away.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#824
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?