Describe the bug

Two separately created Docker volumes mounted into the same container under OrbStack report the same device ID (st_dev) inside the container. This makes distinct persistent volumes appear as the same filesystem device.

To Reproduce

1. Create two Docker volumes:

   docker volume create vol-a
   docker volume create vol-b

2. Run an Alpine container with both volumes mounted:

   docker run --rm -it \
     -v vol-a:/mnt/a \
     -v vol-b:/mnt/b \
     alpine sh

3. Inside the container, check device IDs:

   # stat -c '%d %n' /mnt/a /mnt/b
   38 /mnt/a
   38 /mnt/b

   This suggests both mount points report the same device ID.

Expected behavior

Each Docker volume should have a different device ID, for example:

<dev-1> /mnt/a
<dev-2> /mnt/b

Diagnostic report (REQUIRED)

OrbStack info:
Version: 2.0.5
Commit: cfe47627f138ffd822c958553b0a93eaf2692c71 (v2.0.5)

System info:
macOS: 26.2 (25C56)
CPU: arm64, 10 cores
CPU model: Apple M1 Max
Model: MacBookPro18,2
Memory: 64 GiB

Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2026-02-13T01-47-19.410549Z.zip

Screenshots and additional context (optional)

Why do we need the distinction? It's because we are using google/alloydbomni, which checks the device IDs of the main data directory and the storage cache directory. It will reject configurations in which the storage cache and the data are on the same device.