Code Component of Agent Issues

[Yeon1007]

When I use the agent's code component, regardless what content of my code, it always returns the following exception:

Exception executing code: HTTPConnectionPool(host='none', port=9385): Max retries exceeded with url: /run (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x703942be7130>: Failed to resolve 'none' ([Errno -5] No address associated with hostname)"))

Why is that and how can i fix it? @dosu @Magicbook1108

[dosubot[bot]]

This error happens because the agent's code component tries to send code execution requests to a backend host, but the host is set to 'none' due to a missing or incorrect configuration. The host should be set via the SANDBOX_HOST environment variable, and the code execution backend (RAGFlow Sandbox) must be running and reachable.

To fix this:

1. Make sure the RAGFlow Sandbox is installed and running.
2. Set the environment variable SANDBOX_ENABLED=1.
3. Ensure SANDBOX_HOST is set (it defaults to sandbox-executor-manager when SANDBOX_ENABLED=1).
4. Add this line to your /etc/hosts file if it’s missing:

   127.0.0.1 es01 infinity mysql minio redis sandbox-executor-manager
   

5. Restart all RAGFlow services after making these changes for them to take effect.

If you’re using a remote MinerU service, also set the MINERU_APISERVER environment variable to the correct URL; if it’s unset or set to 'none', you’ll see similar errors.

References:

• Agent code component host config and error cause
• Settings and environment variables
• Official troubleshooting guide

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[Yeon1007]

still shows container is busy, and the log of sandbox container is: ERROR:sandbox: Container creation failed sandbox_python_0: docker: Error response from daemon: client version 1.43 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version. @dosu

[dosubot[bot]]

Your Docker client is too old for the sandbox to create containers—RAGFlow Sandbox requires Docker version 24.0.0 or higher (API 1.44+) and Docker Compose 2.26.1 or higher. This version mismatch is why you see both the "container pool is busy" and the Docker API error: no new containers can be started until you upgrade Docker.

To fix this:

1. Upgrade Docker to at least 24.0.0 and Docker Compose to at least 2.26.1. See the official Docker install guides for Linux, Windows, or macOS.
2. After upgrading, restart the Docker daemon and all RAGFlow services.
3. Run docker version and check that the client API version is at least 1.44.

If you don’t have permission to upgrade Docker, you’ll need to ask your system administrator or IT support to do it for you.

References:

• Sandbox README: Docker >= 24.0.0 required
• Sandbox Quickstart: Docker 24.0.0+ and Compose 2.26.1+ required

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[Yeon1007]

Why is the version of my Docker desktop client different from the client version of the container where my sandbox is located? @dosu

[dosubot[bot]]

The Docker client version inside your sandbox container can be different from your Docker Desktop client because the sandbox-executor-manager container includes its own Docker client binary (for example, version 24.0.7), which is installed independently of whatever Docker client you have on your host or desktop. The container talks to the host's Docker daemon by mounting the Docker socket (/var/run/docker.sock), but the CLI version inside the container is determined by what the container image installs—not what you have on your desktop. This means you might see different client versions reported inside the container versus on your desktop, even though both are communicating with the same Docker server. If you see version mismatch errors, make sure both the Docker client inside the sandbox container and your Docker daemon are up to date and compatible.
Reference: sandbox Dockerfile and compose setup

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[Magicbook1108]

I suggest you to install the latest docker desktop/ docker cli