WebSocket Code Execution Failing in Production

[igortullio]

Problem Description

The WebSocket-based code execution feature (REPL functionality) is not working in production environment. Users can connect via WebSocket but code execution fails, likely due to missing Docker base images that are required for running user code in containers.

Current Behavior

• WebSocket connection establishes successfully
• Code execution fails when trying to run user code in Docker containers
• Error occurs during container creation/execution phase

Expected Behavior

• WebSocket connection should establish
• User code should execute successfully in appropriate language containers
• Output should be streamed back via WebSocket

Root Cause Analysis

After investigating the codebase and testing locally, I identified that the issue is maybe related to missing Docker base images in the production environment.

Local Testing Findings:

• Initially experienced the same issue locally when base images weren't built
• After following the README instructions to build base images locally (docker build -t js-base ., docker build -t py-base ., etc.), the functionality worked correctly
• This confirms the base images are a critical dependency for the REPL functionality

Screenshots/Evidence

• Production: ❌ Fails

• Local: ✅ Works after building base images manually

Priority

High - This affects core functionality of the platform where users submit code for execution.

[satsie]

Prioritizing this so we can verify if it is still an issue

[cassiot]

I'm having this exact error trying to submit CH5VLS4.

I don't know how to advance

[0tuedon]

I'm having this exact error trying to submit CH5VLS4.

I don't know how to advance

were you able to advance this could be because of the Instance issue we did have last week @satsie