langgenius / dify

Dify is an open-source LLM app development platform. Dify's intuitive interface combines AI workflow, RAG pipeline, agent capabilities, model management, observability features and more, letting you quickly go from prototype to production.
https://dify.ai
Other
51.08k stars 7.35k forks source link

Occasionally "Operation not permitted" #9449

Open Kain-90 opened 3 weeks ago

Kain-90 commented 3 weeks ago

Self Checks

Dify version

0.6.16

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

  1. Create the example code execution block
  2. Rapidly click "Run this step" multiple times (about 10 to 30 times)

✔️ Expected Behavior

No error

❌ Actual Behavior

Operation not permitted

image image

dosubot[bot] commented 3 weeks ago

@Kain-90 Hello there! I'm Dosu, a bot here to help you with bug fixes, questions, and becoming a contributor. Let's tackle this issue together while we wait for a human maintainer.

I found some similar issues and discussions related to the "Operation not permitted" error in Dify:

  1. Open Issue: Code block cannot be executed correctly in JavaScript language - This issue is still open and suggests ensuring that directories and files mounted into Docker containers have the correct permissions. It also recommends upgrading the sandbox version to 0.2.6 or later, as some users have reported issues on Mac M1 machines that might be related to the chip architecture [1].

  2. Closed Issue: Using pandas on code block: error: operation not permitted - This issue was resolved by checking the security policies and restrictions in place, as Dify uses DifySandbox to ensure security. It suggests ensuring that pandas is correctly added to the advanced dependencies and checking for any configuration issues [2].

  3. Closed Issue: Workflow run code tool error: operation not permitted - This issue was related to Docker environment permissions. It suggests checking Docker permissions, volume mounts, container user permissions, SELinux/AppArmor policies, and file system permissions. It also mentions reviewing Docker logs for additional insights [3].

For your specific case, you might want to check the permissions and configurations related to your Docker setup, as well as consider upgrading to a newer sandbox version if applicable.

To continue talking to Dosu, mention @dosu.

Kain-90 commented 3 weeks ago

I've read related issues, and some people have encountered the same problem as me, that is, occasional errors, not every time, this issue is marked as complete, but in fact, FAQ does not solve my problem.

crazywoola commented 3 weeks ago

Please upgrade the sandbox to 0.2.10.

Kain-90 commented 3 weeks ago

Please upgrade the sandbox to 0.2.10.

Thanks for your reply.

It's been upgraded to 0.2.10, but i encountered the same issue again, and under the same reproduction conditions, another problem also emerged.

image image image

another problem

image image
Kain-90 commented 2 weeks ago

Please upgrade the sandbox to 0.2.10.

Is there any progress?