docker容器内的attached 和detached模式

### Docker Desktop on Linux Installation and Usage #### Prerequisites for Installing Docker Desktop on Linux To install Docker Desktop, the system must meet certain requirements. The operating system should be a recent version of one of these distributions: Ubuntu (18.04 LTS or later), Fedora (33 or later), Debian (10 or later). Additionally, ensure that virtualization is enabled in BIOS/UEFI settings because it's required by HyperKit which Docker Desktop uses to create VMs[^1]. #### Installation Steps Overview The process involves downloading Docker Desktop from the official website, installing dependencies like HyperKit, and then running an installer package specific to your distribution. For instance, on **Ubuntu**, after ensuring prerequisites are met: ```bash sudo apt-get update && sudo apt-get upgrade -y ``` Install necessary packages including `hyperkit`, `vfio-vsock` kernel module support via APT repository updates as per documentation guidelines provided at Docker’s site. Once all setup scripts complete successfully without errors, launch Docker Desktop through GUI application menus or command line using `com.docker.desktop`. #### Using Docker with Volumes and Containers After successful installation, interacting with containers becomes straightforward. For example, mounting local directories into container environments can be achieved using `-v` flag during runtime commands such as shown below where `${PWD}` represents current working directory path outside container while `/data` specifies internal mount point inside container filesystem structure[^3]: ```bash docker run -d --rm --name qtumd_node1 \ --network=qtum_network \ -v ${PWD}/node1_qtumd.conf:/home/qtum/qtum.conf:ro \ -v ${PWD}/node1_data:/data \ cryptominder/qtum:latest qtumd ``` This command starts a new detached (`-d`) session named `qtumd_node1` within network namespace `qtum_network`. It mounts two volumes read-only configuration file and writable data storage area respectively before executing entrypoint script defined under image tag `cryptominder/qtum:latest`. #### Accessing Running Containers Interacting directly with processes running inside active sessions requires attaching terminal interface linked against target environment. This action utilizes `exec` subcommand alongside specifying shell interpreter type intended for interactive use cases as demonstrated hereunder connecting bash instance attached to previously created service node[^2]: ```bash docker exec -it teamtalk /bin/bash ``` --related questions-- 1. What are common troubleshooting steps when facing issues launching Docker Desktop? 2. How does enabling virtualization improve performance for applications hosted within Docker containers? 3. Can you explain how networks function between host machines and their respective isolated guest instances managed by Docker? 4. In what scenarios would someone prefer utilizing bind mounts over anonymous volumes when configuring persistent storages across multiple services?