Java 10针对Docker的JVM运行优化是否支持其他容器技术？

Great question! Let's clear this up—Java 10's container-aware optimizations aren't tied exclusively to Docker. They're built on standard Linux kernel features that most modern container runtimes rely on, so they work with tools like rkt, Warden, and others, as long as those runtimes use the right underlying mechanisms.

Here's a breakdown of how it works:

• Memory/CPU limit detection: JVM reads resource constraints from Linux cgroups (control groups)—the kernel-level system that all major container tools use to isolate and limit resources. Whether it's Docker, rkt, or Warden setting the limits, as long as they properly configure cgroups for the container, JVM will pick up those values instead of falling back to the host's total resources.
• Container environment detection: JVM doesn't check for Docker-specific markers to know it's running in a container. Instead, it looks for general signs like the presence of cgroup files (under /sys/fs/cgroup) or unusual values in /proc filesystem stats that indicate it's in an isolated environment. Any container runtime that creates a proper isolated cgroup environment will trigger this detection.

A quick note on edge cases: Some older or niche runtimes might not configure cgroups exactly as JVM expects, but for mainstream tools like rkt (which is fully cgroups-compliant) or Warden (used in Cloud Foundry, which has updated to support proper cgroup-based resource limits), these optimizations work just fine.

内容的提问来源于stack exchange，提问作者Nick Suwyn