Skip to content

Conversation

@knowlet
Copy link

@knowlet knowlet commented Feb 14, 2025

Dify Version:

  • Dify: 0.15.3
  • Dify Sandbox: 0.2.10

Deployment Environment:

Self-Hosted (M1 MacBook with OrbStack Docker)

Issue Description

When creating a new workflow and selecting the Code block, after running the JavaScript runtime returns an empty result accompanied by operation not permitted errors, whereas the Python runtime executes normally. Further investigation revealed that under certain conditions, Node.js triggers a failed with signal: bad system call error.

Root Cause and Resolution

Although the exact root cause of the error remains unclear, testing indicates that upgrading the Golang version resolves the issue.

Changes in This PR

  • Golang Upgrade: Bumped Golang to version 1.24.0.
  • Dockerfile Refactoring:
    • Revised the Dockerfile to optimize layer ordering for improved caching.
    • Adjusted the build process to compile inside the Docker container, which minimizes discrepancies caused by environmental differences.
  • CI Process Update: Switched to GitHub-hosted arm runners to standardize the build environment.

This PR should address the issue with the Node.js runtime while also enhancing the overall build reliability and efficiency.

Test the updated version using my DockerHub image:
🔗 DockerHub: knowlet/dify-sandbox:0.2.11

Reference:
langgenius/dify#7687
langgenius/dify#12287

FIx #128

…reation

Refactors GitHub Actions workflow to:
- Support multi-architecture builds for amd64 and arm64
- Implement digest-based build and push strategy
- Add manifest list creation for cross-platform image support
- Dynamically select Dockerfile based on platform
- Improve build artifact management and image tagging
- Use GitHub Actions Hosted ARM runners
@knowlet knowlet changed the title Fix JS runtime operation not permitted issue Fix JS runtime operation not permitted issue in M1 orbstack Feb 14, 2025
@liixing
Copy link

liixing commented Feb 25, 2025

have the same issue here, can someone take a look at this PR?

@Soya-xy
Copy link

Soya-xy commented Mar 27, 2025

have the same issue here!

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.

Node code run failed

4 participants