Isolated Dependencies
Run an environment and model in separate containers so each can keep its own dependencies.
The bring-your-own-container example builds an environment image and a model image separately. Each Dockerfile installs only the packages its side needs. The client connects to both endpoints over RLMesh, so neither process imports the other’s dependencies.
From the RLMesh repository root, build the two images:
docker build -t my-env:latest examples/python/byo_container/env
docker build -t my-model:latest examples/python/byo_container/modelThe container walkthrough shows how to run the images and connect them with rlmesh.session(). To evaluate a different simulator or model stack, change that side’s Dockerfile and entrypoint; the client still uses the same remote environment and model handles.
For the process boundary and lifecycle rules, see Dependency Isolation and Runtime Lifecycle.