sudo orbit shell fails to launch attached to the Orbit osquery socket

[mason-buettner]

Fleet version: 4.77, Orbit 1.50.1

Web browser and operating system: Debian 13

---

💥  Actual behavior

When launching sudo orbit osquery on Debian, an extensions socket is specified in the launch but not attached.

mb@debian:~$ sudo orbit osqueryi
[sudo] password for mb: 
{"level":"info","cmd":"/opt/orbit/bin/osqueryd/linux-arm64/stable/osqueryd -S --pidfile=/opt/orbit/shell/osquery.pid --extensions_socket=/opt/orbit/shell/orbit-osquery.em --database_path /opt/orbit/shell/osquery.db --tls_server_certs /opt/orbit/certs.pem","time":"2025-12-12T14:49:17-08:00","message":"start osqueryd"}
Using a virtual database. Need help, type '.help'
osquery> SELECT * FROM orbit_info;
Error: no such table: orbit_info
osquery> .connect /opt/orbit/orbit-osquery.em
Connected to extension socket /opt/orbit/orbit-osquery.em for debugging
[*]osquery> SELECT * FROM orbit_info;
+---------+--------------------------------------+----------+---------------------+---------------+------------------+-----------------+-----------------+--------+-----------------+-----------------------------+
| version | device_auth_token                    | enrolled | last_recorded_error | orbit_channel | osqueryd_channel | desktop_channel | desktop_version | uptime | scripts_enabled | update_url                  |
+---------+--------------------------------------+----------+---------------------+---------------+------------------+-----------------+-----------------+--------+-----------------+-----------------------------+
| 1.50.1  | <redacted>                           | true     |                     | stable        | stable           | stable          | 1.50.1          | 435    | 1               | https://updates.fleetdm.com |
+---------+--------------------------------------+----------+---------------------+---------------+------------------+-----------------+-----------------+--------+-----------------+-----------------------------+

🛠️ To fix

TODO

🧑‍💻  Steps to reproduce

These steps:

• [x] Have been confirmed to consistently lead to reproduction in multiple Fleet instances.
• [ ] Describe the workflow that led to the error, but have not yet been reproduced in multiple Fleet instances.

1. Launch osqueryi with sudo orbit osqueryi.
2. Attempt to access any tables bundled with Orbit.

🕯️ More info (optional)

N/A