Include the sandbox API
Every custom sandbox image must include thesandbox-api binary:
Correct Dockerfile paths
When you runbl deploy, Blaxel archives all files in your current directory and sends them to the build server. If the Dockerfile is in a subdirectory such as agent-container/, write COPY paths relative to the uploaded build context.
Incorrect:
Reduce build timeouts
Internal timeout increases usually resolve build timeout failures automatically. If timeouts continue:- Install fewer packages in the Dockerfile
- Use a smaller base image where possible
- Combine
RUNinstructions to reduce image layers
Fix custom entrypoints
If your entrypoint checks ports withnc, install netcat:
127.0.0.1 instead of localhost in Debian-based images because localhost may not resolve correctly.
If you do not need custom initialization, remove the custom script and start the sandbox API directly:
Install system libraries
Compilation errors such asunable to find library -lgcc indicate that the image lacks development packages. Install the required toolchain:
Configure the environment
DockerENV variables are available to the entrypoint and its child processes. Extend variables such as PATH with export in your entrypoint script:
Inspect build logs
Use the CLI to view the complete build process and deployment errors:Docker sandbox tutorial
Learn how to run Docker workloads in a sandbox.
Sandbox processes
Learn how to start and manage processes programmatically.