how to check shell environment in virtualbox ,docker , physical machine
result is none means
When executed without --quiet will print a short identifier for the detected virtualization technology. The following technologies are currently identified:
Table 1. Known virtualization technologies (both VM, i.e. full hardware virtualization, and container, i.e. shared kernel virtualization) Type ID Product
VM qemu QEMU software virtualization, without KVM
kvm Linux KVM kernel virtual machine, with whatever software, except Oracle Virtualbox zvm s390 z/VM vmware VMware Workstation or Server, and related products microsoft Hyper-V, also known as Viridian or Windows Server Virtualization oracle Oracle VM VirtualBox (historically marketed by innotek and Sun Microsystems), for legacy and KVM hypervisor powervm IBM PowerVM hypervisor - comes as firmware with some IBM POWER servers xen Xen hypervisor (only domU, not dom0) bochs Bochs Emulator uml User-mode Linux parallels Parallels Desktop, Parallels Server bhyve bhyve, FreeBSD hypervisor qnx QNX hypervisor acrn m[blue]ACRN hypervisorm Container openvz OpenVZ/Virtuozzo
lxc Linux container implementation by LXC lxc-libvirt Linux container implementation by libvirt systemd-nspawn systemd's minimal container implementation, see systemd-nspawn(1) docker Docker container manager podman m[blue]Podmanm container manager rkt rkt app container runtime wsl m[blue]Windows Subsystem for Linuxm proot m[blue]prootm userspace chroot/bind mount emulation pouch m[blue]Pouchm Container Engine
If multiple virtualization solutions are used, only the "innermost" is detected and identified. That means if both machine and container virtualization are used in conjunction, only the latter will be identified (unless --vm is passed).
Windows Subsystem for Linux is not a Linux container, but an environment for running Linux userspace applications on top of the Windows kernel using a Linux-compatible interface. WSL is categorized as a container for practical purposes. Multiple WSL environments share the same kernel and services should generally behave like when being run in a container.