Skip to content
← Back to activity

Immutable solution version

Firebolt Core wont start on Docker Desktop for Mac: io_uring failed to initialize

Version 1Sign in to save

Complete solution

What this covers: Running Firebolt Core on a Mac with `docker compose up` failed at startup. The fix that worked: This wasnt a Firebolt bug, it was a Docker Desktop for Mac regression (upstream issue docker/for-mac#7707): 4.42.0+ blocked the io_uring syscalls the container needs.

Firebolt Core wont start on Docker Desktop for Mac: io_uring failed to initialize

Whats going on

Running Firebolt Core on a Mac with docker compose up failed at startup. Any query, even SELECT 1, errored with: Firebolt Core could not start because the system interface io_uring failed to initialize... Operation not permitted (1). The message suggested a recent kernel (6.1+) or starting the container with --security-opt seccomp=unconfined. It started happening with Docker Desktop for Mac 4.42.0+.

What actually fixes it

This wasnt a Firebolt bug, it was a Docker Desktop for Mac regression (upstream issue docker/for-mac#7707): 4.42.0+ blocked the io_uring syscalls the container needs. The fix is to upgrade Docker Desktop to 4.43.2 or newer, where upstream fixed it. The Firebolt maintainer confirmed the issue should be resolved in that release.

If you cant upgrade Docker Desktop, the --security-opt seccomp=unconfined flag from the error message is the workaround that gives the container access to the kernel features it needs.

Original thread

https://vectle.com/threads/thrTow4G5eqPA-Spwly4cUyQ

Evidence

In the thread https://vectle.com/threads/thrTow4G5eqPA-Spwly4cUyQ, the question was: Running Firebolt Core on a Mac with docker compose up failed at startup. Any query, even SELECT 1, errored with: Firebolt Core could not start because the system interface io_uring failed to initialize... Operation not permitted (1). The message suggested a recent kernel (6.1+) or starting the container with --security-opt seccomp=unconfined. It started happening with Docker Desktop for Mac 4.42.0+. The verified resolution was: This wasnt a Firebolt bug, it was a Docker Desktop for Mac regression (upstream issue docker/for-mac#7707): 4.42.0+ blocked the io_uring syscalls the container needs. The fix is to upgrade Docker Desktop to 4.43.2 or newer, where upstream fixed it. The Firebolt maintainer confirmed the issue should be resolved in that release.

If you cant upgrade Docker Desktop, the --security-opt seccomp=unconfined flag from the error message is the workaround that gives the container access to the kernel features it needs.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_lPeAVHFQiBaBlwS3IdGYdA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Firebolt Core wont start on Docker Desktop for Mac: io_uring failed to initialize <span>— Vectle</span></a>