Codespace with custom linux kernel

[h7x4]

Select Topic Area

Question

Body

Hello!

I'm working on a project that uses USBIP to forward traffic between a codespace and yourself. Unfortunately, I've hit a roadblock where USBIP requires a kernel module called vhci-hcd, which usually comes included in linux-image-generic. I'm guessing that linux-azure has been built without USB support. So before diving into DKMS modules and alternative solutions, I thought I'd ask whether it is possible to switch out the kernel.

So far, i've tried installing linux-image-5.19.0-46-generic through the ubuntu repositories and rebooting the VM using the magic sysrq trick, but everything just seems to break. When it resolves after a few minutes, it's back to the azure kernel.

I expect the answer to be no, but I thought I'd ask anyway.

I think this would also answer #12766, no matter if it's a no or a yes.

Edit:
My guess about the kernel being built without USB support was wrong. It does indeed have USB support. According to linux-headers-5.15.0-1041-azure, the missing piece is CONFIG_USBIP_CORE, and thereby CONFIG_USBIP_VHCI_HCD. I think this will make my life a lot easier if I decide to go the DKMS module route. But it doesn't really add anything to the original question.

[jkeech]

So far, i've tried installing linux-image-5.19.0-46-generic through the ubuntu repositories and rebooting the VM using the magic sysrq trick, but everything just seems to break. When it resolves after a few minutes, it's back to the azure kernel.

It's not possible to modify the kernel, reboot, and have the changes persist. Every time a codespace is restarted, it's on a fresh VM host with the image controlled by the Codespaces platform.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[crias-solutions]

I guess a few years later, the Kernel limitation is still the same:

• GitHub Codespaces runs on an Azure-optimized kernel that does not include the vhci-hcd kernel module required for USB/IP client functionality.
  This means direct USB device attachment in the browser-based Codespace is not possible.