[PR #16189] chore: to expand compatibility with Docker versions. #28453

Closed
opened 2026-02-21 20:43:29 -05:00 by yindo · 0 comments
Owner

Original Pull Request: https://github.com/langgenius/dify/pull/16189

State: closed
Merged: No


Summary

When migrating from Docker 23.0.3 to 20.10.9, it was discovered that three containers(worker, sandbox, api) encountered the following error:

runtime/cgo: pthread_create failed: Operation not permitted SIGABRT: abort

I have noticed that there are differences in the default seccomp settings across different versions of Docker. Some Docker versions default to blocking pthread_create. Therefore, I have made modifications based on the official default seccomp profile to allow the execution of pthread_create. Additionally, I have overridden the default seccomp settings in the docker-compose files for the worker, api, and sandbox containers to ensure they can start and run properly in most Docker environments.

Fix https://github.com/langgenius/dify/issues/17312

Tip

Close issue syntax: Fixes #<issue number> or Resolves #<issue number>, see documentation for more details.

Screenshots

Before After
error1error2 ...

Checklist

Important

Please review the checklist below before submitting your pull request.

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/16189 **State:** closed **Merged:** No --- # Summary When migrating from Docker 23.0.3 to 20.10.9, it was discovered that three containers(worker, sandbox, api) encountered the following error: `runtime/cgo: pthread_create failed: Operation not permitted SIGABRT: abort` I have noticed that there are differences in the default seccomp settings across different versions of Docker. Some Docker versions default to blocking pthread_create. Therefore, I have made modifications based on the official default seccomp profile to allow the execution of pthread_create. Additionally, I have overridden the default seccomp settings in the docker-compose files for the worker, api, and sandbox containers to ensure they can start and run properly in most Docker environments. Fix https://github.com/langgenius/dify/issues/17312 > [!Tip] > Close issue syntax: `Fixes #<issue number>` or `Resolves #<issue number>`, see [documentation](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) for more details. # Screenshots | Before | After | |--------|-------| | <img width="844" alt="error1" src="https://github.com/user-attachments/assets/95ccf808-e317-4466-b57e-0601d793cdcc" /><img width="699" alt="error2" src="https://github.com/user-attachments/assets/579e9d55-a8fa-4335-a669-8e713b7e3ab0" /> | ... | # Checklist > [!IMPORTANT] > Please review the checklist below before submitting your pull request. - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:43:29 -05:00
yindo closed this issue 2026-02-21 20:43:29 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#28453