-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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
'base64' module not found in the sandbox environment. #14371
Comments
@SharkSyl Hello there! I'm here to assist you with any bugs, questions, or contributions you may have. Let's tackle this issue together! The To resolve this, you can try adding the If the issue persists, it might be worth checking if there are any specific configurations or restrictions in the sandbox environment that could be affecting the import of standard Python modules. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
@dosu docker-compose exec sandbox bash
root@eb9eebfe1b77:/# python3
Python 3.10.14 (main, Apr 24 2024, 12:40:18) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import base64
>>> |
Could you provide more details about the specific code block or script you're trying to run in the sandbox environment that results in the To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
Please open an issue here instead https://github.com/langgenius/dify-sandbox |
Self Checks
Dify version
langgenius/dify-sandbox:0.2.10
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
The error below occurs when running a code block in the workflow.
I used a Docker image: 'langgenius/dify-sandbox:0.2.10'
Is it an issue with version 0.2.10?"
✔️ Expected Behavior
The code should execute successfully.
❌ Actual Behavior
same with Issue 8151
The text was updated successfully, but these errors were encountered: