Skip to main content

On This Page

DDEV 1.25.0 Review: Experimental Podman and Docker Rootless Support

2 min read
Share

These articles are AI-generated summaries. Please check the original sources for full details.

Review: DDEV 1.25.0 — Experimental Podman and Docker Rootless Support

DDEV 1.25.0 ships experimental support for Podman and Docker rootless, opening up new corporate-friendly runtimes while introducing practical trade-offs. The Podman and rootless workflows depend on specific global settings for ports and mount modes that must be audited before implementation.

Why This Matters

Adopting rootless runtimes requires reconciling ideal container architecture with the technical reality of OS-level restrictions. Specifically, Podman on macOS and Docker rootless environments cannot utilize privileged ports or traditional bind mounts, forcing teams to move away from standard configurations like port 80/443 to maintain system security and compatibility.

Key Insights

  • Podman on macOS cannot bind to privileged ports 80/443, requiring DDEV router ports to be set to 8080/8443 (2026).
  • Docker rootless mode is incompatible with host bind mounts, necessitating the use of the no-bind-mounts configuration mode (DDEV 1.25.0).
  • Global configuration settings for these runtimes are managed via the global_config.yaml file located in the $HOME/.ddev directory.
  • DDEV 1.25.0 experimental support enables developers to use corporate-friendly runtimes while requiring a shift in workstation configuration (2026).

Practical Applications

  • Use Case: macOS developers using Podman must adjust global_config.yaml to use ports 8080 and 8443. Pitfall: Standard port 80/443 binding attempts will fail due to macOS security restrictions on non-root processes.
  • Use Case: Engineering teams deploying Docker rootless must enable no-bind-mounts mode in their global configuration. Pitfall: Attempting to use default bind mounts will lead to container initialization errors and volume mapping failures.

References:

Continue reading

Next article

Leveraging EKS Capabilities for Managed Kubernetes Infrastructure and Resource Orchestration

Related Content