Skip to main content

​
Auto-detection (no Dockerfile needed)

By default, floo uses Railpack to auto-detect your runtime from project files and build automatically. No Dockerfile required.
FileDetected runtime
package.json + nextNode.js (Next.js)
package.json + viteNode.js (Vite)
package.json + expressNode.js (Express)
requirements.txt / pyproject.toml + fastapiPython (FastAPI)
requirements.txt / pyproject.toml + flaskPython (Flask)
requirements.txt / pyproject.toml + djangoPython (Django)
go.modGo
index.html (no backend)Static HTML
floo deploy --dry-run shows what was detected without deploying.

​
When to write a Dockerfile

Use a Dockerfile when you need:
  • Custom build steps (e.g., code generation, asset compilation)
  • Multi-stage builds for smaller images
  • Non-standard runtimes or system dependencies
  • Specific base image requirements
If a Dockerfile is present in your project root, floo uses it directly — no auto-detection.

​
Cached base images

floo provides pre-cached base images hosted in floo’s container registry. These are pulled instantly during builds, cutting build times significantly.
ImageTags
floo-base-node20, 22
floo-base-python3.12, 3.13
floo-base-ruby3.3
floo-base-go1.23
Use the short form in your Dockerfile: 
FROM floo-base-node:22
The build system resolves floo-base-* to the full registry URI (us-docker.pkg.dev/floo-prod/floo-images/...) automatically. List all available images: 
floo images list

​
Example: Node.js with floo-base-node

FROM floo-base-node:22 AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build

FROM floo-base-node:22
WORKDIR /app
COPY --from=builder /app/.next ./.next
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./
EXPOSE 3000
CMD ["npm", "start"]

​
Example: Python with floo-base-python

FROM floo-base-python:3.13
WORKDIR /app
COPY requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt
COPY . .
EXPOSE 8000
CMD ["uvicorn", "main:app", "--host", "0.0.0.0", "--port", "8000"]
See the floo images CLI reference for the full list of available images and their URIs.