webdev-custom-dockerfile

Write deploy-compatible custom Dockerfiles for Manus webdev fullstack projects requiring extra binaries or runtimes.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/AnderHonorato/Mem-rias-IA---Infinity --skill webdev-custom-dockerfile-anderhonorato
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webdev-custom-dockerfile
Source: https://github.com/AnderHonorato/Mem-rias-IA---Infinity/tree/main/Manus/Skills/webdev-custom-dockerfile
Command: npx skills add https://github.com/AnderHonorato/Mem-rias-IA---Infinity --skill webdev-custom-dockerfile-anderhonorato

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Manus webdev (web-db-user) project needs a system binary like ffmpeg or chromium, or another language runtime like Python, Java, Go, or Rust in production, the auto-generated deploy image is not enough. This Skill defines the exact deploy contract a custom root Dockerfile must satisfy so the build succeeds within platform limits. ## Core Features & Use Cases - Deploy contract rules: Covers build context contents, automatic secrets injection after every FROM line, the ~300-second Cloud Build budget, .dockerignore behavior, and the 1 vCPU / 512 MiB runtime envelope. - Base image guidance: Explains when to stay on node:22-slim with apt packages versus inverting to another runtime's official image (eclipse-temurin, golang, rust) and adding Node via NodeSource. - Worked examples: Provides ready Dockerfile patterns for headless Chromium with puppeteer, Java runtime, and multi-stage Go/Rust builds with libc-mismatch avoidance, plus a pre-deploy checklist. - Use Case: Your app must convert uploaded videos with ffmpeg in production. Use this Skill to write a root Dockerfile based on node:22-slim that installs ffmpeg, runs the full pnpm build in-image, keeps node_modules, and listens on process.env.PORT. ## Quick Start Ask the AI to write a production Dockerfile for this webdev project that adds the system binary or language runtime you need, following the deploy contract.

Frequently Asked Questions about webdev-custom-dockerfile

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

FAQPage Schema
How do I add ffmpeg or chromium to a Manus webdev deployment?

Create a Dockerfile at the project root based on node:22-slim and apt-get install the needed packages such as ffmpeg, chromium, or fonts-noto-cjk. The image must run the full pnpm build itself and keep node_modules, since the platform no longer builds the frontend separately.

When should I write a custom Dockerfile for deployment?

Only when production needs an extra system binary or another language runtime like Python, Java, Go, or Rust. A custom Dockerfile does not make deploys faster or more reliable, since the auto-generated image already does a corepack-pinned install with cached layers.

How do I use puppeteer in a Docker container without downloading Chromium?

Install chromium via apt on node:22-slim and set PUPPETEER_SKIP_DOWNLOAD=true with PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium. Launch with --no-sandbox --disable-setuid-sandbox --disable-dev-shm-usage and reuse one browser instance across requests to stay within the 512 MiB memory limit.

Can I add Java or Go to a Node.js deploy image?

Yes. For Java, start FROM eclipse-temurin:21-jre and add Node via the NodeSource script. For Go or Rust, build a static binary in a separate stage and copy only the binary into the node:22-slim runtime stage, avoiding libc mismatches between musl and glibc.

Why does my Docker build fail or time out on deployment?

Cloud Build enforces a hard ~300-second timeout including base image pulls, and intermediate multi-stage layers rebuild from scratch on every deploy. Read the last 6000 characters of the build log returned in the deploy result, then trim compilation work or use prebuilt binaries.

Should I put secrets like DATABASE_URL in my Dockerfile?

Never. The platform automatically injects all project secrets as ENV after every FROM line at build time and provides them at runtime. Writing secret literals or copying .env files is prohibited, and .env files are excluded from the build context anyway.