# Issues on Step 2: Start the Evaluation Container
**URL:** https://discourse.openrobotics.org/t/issues-on-step-2-start-the-evaluation-container/53668
**Category:** AI for Industry Challenge
**Created:** [March 30, 2026, 7:28pm UTC](https://discourse.openrobotics.org/t/issues-on-step-2-start-the-evaluation-container/53668 "2026-03-30T19:28:27Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@J\_Zhang](https://discourse.openrobotics.org/u/J_Zhang)
#### Post date: [March 30, 2026, 7:28pm UTC](https://discourse.openrobotics.org/t/issues-on-step-2-start-the-evaluation-container/53668/1 "2026-03-30T19:28:27Z")
Hello, I’m following the ‘Getting Started‘ instructions. I’ve set up Docker, Distrobox, Pixi, Nvidia Container Toolkit; and Workspace. Right now I’m stuck at Step 2: Start the Evaluation Container.
Everything looks good; but the last step: /entrypoint.sh ground\_truth:=false start\_aic\_engine:=true
Looks good so far: I see Gazebo and RVix open with robot showing; in the terminal showing ‘AIC engine initialized successfully!’
And it continue ‘Starting AIC Engine Run Total Trials: 3‘ and ‘Starting trial \_1‘
log: ‘No node with name ‘aic\_model‘ found. Retrying… ‘ appear with some warning and other INFO.
and other a lot of INFO
with SEVERE WARNING!!! and fatal IO error,
and Aborted with EEOR; and Participand model is not ready for trial\_1
with some warnings and then Trial\_1 failed or was not completed. Score: 0. Then trial\_2
Then: No node with name ‘aic\_model’ found. Retrying… with
✗ Participant model is not ready for trial ‘trial\_2’
And ⚠ Trial ‘trial\_2’ failed or was not completed. Score: 0.000000. Continuing to next trial…
Trial\_3 with Error
Finally Trial ‘trial\_3’ failed or was not completed. Score: 0. and Show Complete Scoring Results
End with INFO and won’t exit logging.
I was supposed to continue with Step 3: **Run an Example Policy**. when exiting the log. But it won’t.
* * *
Can anyone feedback any clue please?
I’m on WSL2 and couldn’t active Nvidia GPU acceleration. As I know to use Nvidia GPU under WSL is different, as requires NVIDIA CUDA Toolkit inside Ubuntu instead of driver (for Windows). [xtra info]
Can anyone help please? Or this is related to WSL vs linux OS?
---
### Author:  [@No\_Quarter\_Robotics](https://discourse.openrobotics.org/u/No_Quarter_Robotics)
#### Post date: [March 31, 2026, 11:26am UTC](https://discourse.openrobotics.org/t/issues-on-step-2-start-the-evaluation-container/53668/2 "2026-03-31T11:26:45Z")
Hello, are you starting the policy in another terminal? Soon as Rviz starts, start the policy in another terminal.. This is the way I do it.
---
### Author:  [@J\_Zhang](https://discourse.openrobotics.org/u/J_Zhang)
#### Post date: [March 31, 2026, 8:11pm UTC](https://discourse.openrobotics.org/t/issues-on-step-2-start-the-evaluation-container/53668/3 "2026-03-31T20:11:05Z")
Thx! @No_Quarter_Robotics
This is the solution. One following Question: Do we have to enter the same ‘aic\_eval‘ container to run the example policy in Step 3?
---
### Author:  [@No\_Quarter\_Robotics](https://discourse.openrobotics.org/u/No_Quarter_Robotics)
#### Post date: [March 31, 2026, 9:40pm UTC](https://discourse.openrobotics.org/t/issues-on-step-2-start-the-evaluation-container/53668/4 "2026-03-31T21:40:30Z")
yes, this is my setup.
#1
sudo mount --make-rshared /
distrobox enter -r aic\_eval
cd ~/ws\_aic
/entrypoint.sh ground\_truth:=true start\_aic\_engine:=true
#2
distrobox enter -r aic\_eval
cd ~/ws\_aic/src/aic
source /opt/ros/kilted/setup.bash
PYTHONPATH=$PWD pixi run ros2 run aic\_model aic\_model --ros-args -p use\_sim\_time:=true -p policy:=nqr\_policies.InsertCable04
---
### Author:  [@Andrew\_Garrett](https://discourse.openrobotics.org/u/Andrew_Garrett)
#### Post date: [March 31, 2026, 10:24pm UTC](https://discourse.openrobotics.org/t/issues-on-step-2-start-the-evaluation-container/53668/5 "2026-03-31T22:24:55Z")
@J_Zhang you don’t need to enter the container to run the policy. After running `pixi install` in the root of the AIC repo, you can run the last command @No_Quarter_Robotics shared on the host (i.e. not in the distrobox container).
I recommend using a shell script that spawns a tmux session with at least two tabs, where one tab enters the distrobox and starts the sim, while the other tab(s) starts your policy and any other ros nodes you’d like to run.