No module named 'json' error

[kiedeng]

I have deployed the Sanbox local source code, and I have updated the python_path to the path of the Miniconda virtual environment (python_path=/root/miniconda3/envs/sanbox/bin/python). However, when I actually use it, it still reports a 'No module named 'json'' error
If I'm deploying with Miniconda, is this configuration not workable?

[zenorochaV1]

same

[cabbage217]

same

[kkjinping]

same

[AegonT]

same

[18827555809]

I have deployed the Sanbox local source code, and I have updated the python_path to the path of the Miniconda virtual environment (python_path=/root/miniconda3/envs/sanbox/bin/python). However, when I actually use it, it still reports a 'No module named 'json'' error If I'm deploying with Miniconda, is this configuration not workable?

I haven't tried your scenario, but I can roughly guess the reason for the problem, mainly related to the location of Python. When building the project, the Python related environment will be copied to/var/sandbox/sandbox-python. The location you provided is:/root/miniconda3/envs/sanbox/bin/python， So it will be copied to/var/sandbox/sandbox-python, and you need to check if there is/var/sandbox/sandbox-python/var/local/lib/python3.XX/site-packages under /var/sandbox/sandbox-python related dependencies

[AegonT]

I resolved this issue through the following steps:

Start the Image:
First, I launched the sandbox image to access the container environment:

docker start <container_name>
docker exec -it <container_name> /bin/bash

Modify the Default Python Path:
Inside the image, I located the system’s default Python path and changed it to the Python path installed in Miniconda. This ensures the container uses Miniconda’s Python environment instead of the system’s default Python.

Check the current Python path:

which python

Update the PATH environment variable to point to Miniconda’s Python:

export PATH="/path/to/miniconda/bin:$PATH"

Verify the change:

which python

Save the Changes:
To make the changes persistent, I updated the container’s configuration or saved it as a new image:

docker commit <container_id> <new_image_name>

Restart the Image:
Finally, I restarted the image to verify the modifications:

docker stop <container_name>
docker start <container_name>
docker exec -it <container_name> /bin/bash
which python  # Confirm the Python path is correctly set

By following this approach, I successfully switched the Python environment of the sandbox image to Miniconda, resolving the related issue.