Light-weight Desktop (desktop-lite) feature not working

[matthewruzzi]

Select Topic Area

Question

Body

I get an error message every time I try to use the Light-weight Desktop (desktop-lite) dev container feature. I have tried it with both the Default Linux Universal (universal) and Node.js & JavaScript (javascript-node) base image templates. Has anyone been able to get it working in 2026?

[Avik-Das-567]

Yes, desktop-lite still works in 2026, but only in specific environments.
Most failures come from trying to use it in unsupported Codespaces setups rather than from the feature itself being broken.

Why this happens

The desktop-lite feature relies on:

• KasmVNC / noVNC

• Systemd + X11

• Privileged container capabilities

GitHub Codespaces intentionally restricts some of these for security and performance reasons. As a result:

• desktop-lite does not work reliably in GitHub-hosted Codespaces

• It does work in:

  • Local Docker (VS Code Dev Containers)

  • Self-hosted Codespaces / custom runners

  • Cloud VMs where Docker runs with elevated privileges

This affects all base images (including universal and javascript-node) because the limitation is at the host level, not the image level.

Common failure modes you’ll see

Depending on the environment, errors usually involve:

• VNC server failing to start

• Missing /run/systemd

• Permission errors around dbus, Xorg, or /dev/shm

These are symptoms of restricted container capabilities, not misconfiguration.

What does work in GitHub Codespaces

If your goal is GUI-like workflows in Codespaces, these are supported alternatives:

• VS Code web-based tooling (extensions instead of desktop apps)

• Browser-based UIs (e.g., Jupyter, Storybook, admin panels)

• Remote desktop to an external VM, not inside the Codespace

GitHub Codespaces is optimized for editor-centric development, not full Linux desktops.

Recommendation

If you need a desktop environment:

• Use desktop-lite locally with Dev Containers.

• Or run it on a self-managed VM where Docker has full privileges.

If you’re staying on GitHub-hosted Codespaces, it’s best to avoid desktop-lite and design workflows around web or VS Code-native tools.

TL;DR

• desktop-lite still works in 2026.

• It's not supported on GitHub-hosted Codespaces.

• Base image doesn’t matter, host restrictions do.

Hope this saves someone else a few hours of debugging.

[matthewruzzi]

Do I need a Dockerfile? The following devcontainer.json fails with the same yarn GPG error.

{
	"image": "mcr.microsoft.com/devcontainers/universal:2",
	"features": {
		"ghcr.io/devcontainers/features/desktop-lite:1": {}
	}
}

[naourass]

You're using the image that has the expired yarn GPG issue directly without updating its yarn package source. You need the two following files inside .devcontainer to fix it. The devcontainer.json config set to a dockerfile build, and the actual Dockerfile config based on the universal image:

devcontainer.json:

{
	"build": {
        "dockerfile": "Dockerfile"
    },
	"features": {
		"ghcr.io/devcontainers/features/desktop-lite:1": {}
	}
}

Dockerfile:

FROM mcr.microsoft.com/devcontainers/universal:2
USER root
RUN rm -f /etc/apt/sources.list.d/yarn.list \
    && rm -f /usr/share/keyrings/yarn.gpg \
    && apt-get update

[matthewruzzi]

The issue about this is marked as resolved. Does that mean that it is not actually resolved?
devcontainers/images#1752 (comment)

[naourass]

That issue is marked resolved for the python image, but it looks like it's not actually resolved for the universal:2 image (the one that you're trying to use here).

[Avik-Das-567]

Seems like you're supposed to use the mcr.microsoft.com/devcontainers/universal:5 version or the mcr.microsoft.com/devcontainers/universal:latest , since it's the version 5- for the universal images, as told in devcontainers/images#1752 (comment)

I guess the issue is actually resolved.

[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! 💬

[rahull2509]

I faced a similar issue where the desktop-lite interface failed to load properly. In my case, it was caused by browser/VPN issues and resource limits. Switching browsers, disabling VPN, and rebuilding the Codespace resolved it. If the issue persists, recreating the Codespace or opening it in VS Code desktop can help.