What problem does it solve? When a Manus webdev fullstack project needs production capabilities beyond the auto-generated deploy image — such as ffmpeg, Chromium, CJK fonts, or a second language runtime like Java, Go, or Rust — you must supply a custom root Dockerfile that satisfies the platform's strict build contract (300-second build budget, 512 MiB runtime, secret injection, committed-only build context). ## Core Features & Use Cases - Deploy Contract Reference: Explains how the platform consumes a root Dockerfile, including build context rules, forced .dockerignore contents, secret ENV injection after every FROM line, and layer-cache behavior. - Base Image Guidance: Provides decision rules for choosing node:22-slim versus inverting to another runtime's official image (eclipse-temurin, golang, rust), with libc-mismatch warnings. - Worked Examples: Includes ready Dockerfile patterns for headless Chromium with puppeteer, Java runtime with Node via NodeSource, and multi-stage Go builds copying a static binary. - Use Case: Your app must convert uploaded videos with ffmpeg in production. Use this Skill to write a node:22-slim-based Dockerfile that apt-installs ffmpeg, runs the full pnpm build in-image, keeps node_modules, and fits the cold-builder time budget. ## Quick Start Ask the AI to write a deploy-compatible Dockerfile for the project that adds the system binary or runtime you need, following the platform's build and runtime rules.
