-
Bug
-
Resolution: Won't Fix
-
P4
-
16, 17
-
linux
hs_err log and `VM.info` dcmd shows cgroup information as container information even though the process run on non-container environment as following.
```
container (cgroup) information:
container_type: cgroupv2
cpu_cpuset_cpus: not supported
cpu_memory_nodes: not supported
active_processor_count: 4
cpu_quota: not supported
cpu_period: not supported
cpu_shares: not supported
memory_limit_in_bytes: unlimited
memory_and_swap_limit_in_bytes: unlimited
memory_soft_limit_in_bytes: unlimited
memory_usage_in_bytes: 164163584
memory_max_usage_in_bytes: not supported
```
We can use cgroup outside of container, so it is useful to show. However cgroup is different from container. We should distinguish them.
```
container (cgroup) information:
container_type: cgroupv2
cpu_cpuset_cpus: not supported
cpu_memory_nodes: not supported
active_processor_count: 4
cpu_quota: not supported
cpu_period: not supported
cpu_shares: not supported
memory_limit_in_bytes: unlimited
memory_and_swap_limit_in_bytes: unlimited
memory_soft_limit_in_bytes: unlimited
memory_usage_in_bytes: 164163584
memory_max_usage_in_bytes: not supported
```
We can use cgroup outside of container, so it is useful to show. However cgroup is different from container. We should distinguish them.
- relates to
-
JDK-8261242 [Linux] OSContainer::is_containerized() returns true when run outside a container
-
- Resolved
-
- links to
-
Review openjdk/jdk/3280