Paketo Buildpacks are CNCF-backed buildpacks that turn source code into optimized container images. Miget uses Paketo to automate detection, dependency installation, layering, and security hardening so you can focus on application code.

​
Supported Languages

Paketo Buildpacks cover a broad set of languages and frameworks:
  • Java: JVM workloads, including Spring Boot, Grails, and Micronaut
  • Node.js: Dependency installation and runtime configuration
  • Python: Django, Flask, and other Python frameworks
  • Go: Minimal-overhead binaries built with Go toolchains
  • PHP: Laravel, Symfony, and other PHP stacks
  • Ruby: Ruby on Rails and other Rack-based apps
  • .NET: Cross-platform .NET applications
The language-specific guides in the Languages → Buildpacks section explain how to configure these runtimes on Miget.

​
Workflow Overview

​
Detection Phase

  • Paketo analyzes your repository to determine which buildpacks apply based on language and framework metadata.

​
Build Phase

  • Staging environment: Dependencies are installed and the app is compiled in an isolated build container.
  • Layered filesystem: Output is organized into reusable layers (OS base, dependencies, app code) for faster rebuilds.
During the build phase, the builder runs with UID 1000 to keep file ownership consistent and secure.

​
Export Phase

  • Image creation: Buildpacks assemble the layers into a runnable image with an entrypoint command.
  • Runtime user: Images run as UID 1001 by default on Miget. The runtime securityContext enforces runAsNonRoot, UID/GID 1000, and fsGroup 1000 for isolation.
securityContext:
  runAsNonRoot: true
  runAsUser: 1001
  runAsGroup: 1000
  fsGroup: 1000

​
Use Cases

​
Web Applications

Rapidly deploy web apps with dependencies and build steps managed automatically.

​
Microservices

Ensure consistent builds across dozens of services with repeatable, layered images.

​
Legacy Applications

Containerize older apps without rewriting Dockerfiles by letting Paketo detect build steps.

​
Advantages over Custom Dockerfiles

​
Abstraction of Complexity

Focus on code rather than crafting and maintaining Dockerfiles for each service.

​
Consistency and Standardization

Standard buildpacks keep environments aligned between development, CI, and production.

​
Enhanced Security

Regularly patched dependencies, detailed BOMs, and non-root defaults improve security posture.

​
Learn More

  • Browse language-specific configuration guides in Languages → Buildpacks
  • Review Miget’s Build Methods to compare Paketo vs. Dockerfile workflows
  • Visit paketo.io for the full specification and release notes