Bug ID: JDK-8264482 container info misleads on non-container environment

Type: Bug
Component: hotspot
Sub-Component: runtime
Affected Version: 16,17

Priority: P4
Status: Open
Resolution: Unresolved
OS: linux

Submitted: 2021-03-31
Updated: 2021-11-16

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

Other
tbdUnresolved

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.