dockerfile

Design Dockerfiles with /start.sh and /terminate.sh for sandbox-ready containers.

31|4|Updated Oct 8, 2025
One-click install
npx skills add https://github.com/ReinforceNow/reinforcenow-cli --skill dockerfile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dockerfile
Source: https://github.com/ReinforceNow/reinforcenow-cli/tree/main/project8/.claude/skills/dockerfile
Command: npx skills add https://github.com/ReinforceNow/reinforcenow-cli --skill dockerfile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams craft Dockerfiles for sandboxed environments with reliable startup and teardown patterns, enabling automated tool runs in controlled containers.

Core Features & Use Cases

  • Sandbox-ready Dockerfile templates: standardized patterns for building containers that host sandboxed tools.
  • Lifecycle management: guidance to implement /start.sh and /terminate.sh to initialize and clean up resources.
  • Best practices: non-root images, port exposure, and platform constraints to ensure predictable behavior.

Quick Start

Use this skill to scaffold a Dockerfile that starts a service on port 8931 and includes /start.sh and /terminate.sh scripts. Then build and run your sandbox container with the recommended commands:

  • Create a Dockerfile following the conventions in the skill
  • Add /start.sh to initialize your service and run the main command
  • Add /terminate.sh to clean up resources before container termination
  • Build: docker build --platform linux/amd64 -t sandbox:latest .
  • Run: docker run --rm -p 8931:8931 sandbox:latest

Frequently Asked Questions about dockerfile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Dockerfile for sandbox containers with automated tooling?

To create a sandbox-ready Dockerfile, design standardized templates that implement /start.sh and /terminate.sh scripts to manage container lifecycle, ensuring reproducible and isolated test environments for automated tool execution.

What are the best practices for building a sandbox-ready Dockerfile?

Best practices for sandbox-ready Dockerfiles include configuring non-root user images, exposing required ports like 8931, implementing /start.sh for initialization and /terminate.sh for cleanup, and specifying platform constraints such as linux/amd64 for predictable behavior.

How do I manage startup and shutdown sequences in a Docker container?

Manage Docker container startup and shutdown by implementing /start.sh to initialize services and run main commands, and /terminate.sh to clean up resources before termination, ensuring a controlled lifecycle for automated tool runs.

Does a sandbox container need to run as a non-root user?

Yes, sandbox containers should run as a non-root user to ensure predictable behavior and security. This pattern is recommended alongside port exposure and platform-specific considerations for reliable container operations.

How do I build and run a sandbox container on a specific platform?

Build and run a sandbox container using platform-specific commands: docker build --platform linux/amd64 -t sandbox:latest . to build, and docker run --rm -p 8931:8931 sandbox:latest to run the isolated environment.

When do I need to use /start.sh and /terminate.sh scripts in Docker?

Use /start.sh and /terminate.sh scripts when creating sandbox-ready containers for automated tooling that require a controlled lifecycle, enabling proper initialization of services and resource cleanup during termination sequences.