Skip to content

chore: let QEMU choose the disk I/O backend unless DISK_IO is set - #8

Merged
vaggeliskls merged 1 commit into
mainfrom
chore/disk-io-auto
Oct 7, 2026
Merged

vaggeliskls merged 1 commit into
mainfrom
chore/disk-io-auto

Conversation

@vaggeliskls

Copy link
Copy Markdown
Owner

Current Behaviour

Since 2.0.1 docker-compose.yml forces DISK_IO=native for every host, trading the faster io_uring path on recent kernels for a guaranteed boot on kernels before 5.12.

Expected Behaviour

  • docker-compose.yml passes DISK_IO through empty unless it is set in .env, so QEMU chooses the backend (io_uring on recent kernels).
  • .env.example and the README table document the three values and tell users on kernels before 5.12 (Ubuntu 20.04) to set DISK_IO=native, since those fail at boot with Failed to initialize io_uring.

docker compose config resolves to an empty value when unset and to native when set in .env.

2.0.1 forced DISK_IO=native. The compose file now passes DISK_IO through
empty, so QEMU picks (io_uring on recent kernels), and hosts with a kernel
before 5.12 set DISK_IO=native in .env, as documented in .env.example and
the README.
@vaggeliskls
vaggeliskls merged commit 19d2c45 into main Oct 7, 2026
1 check passed
@vaggeliskls
vaggeliskls deleted the chore/disk-io-auto branch October 7, 2026 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant