logo

mviereck/x11docker

Run GUI applications and desktops in docker and podman containers. Focus on security.

View on GitHub ↗Jump to charts ↓

mviereck/x11docker has 6k+ stars and 400+ forks on GitHub, is written in Shell, and was last pushed on Jul 5, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 18 minutes ago
Type:CLI ToolCategory(s):Containers & RuntimesDesktop & System UtilitiesCloud Native & Infrastructure
Added to GitGenius on September 10th, 2026
Created on September 24th, 2015
Open Issues & Pull Requests: 31 (+0)
GitHub issues: Enabled
Number of forks: 419
Total Stargazers: 6,335 (+0)
Total Subscribers: 90 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.0 days
Mean response time: 131.0 days
90th percentile: 470.1 days
Tracked items: 77

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 2 days, while "question" waits about 10 days. Three people close 90% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 23
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 176 days
Stale 30+ days: 23
Stale 90+ days: 14

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • question (28)
  • bug (16)
  • enhancement (8)
  • needinfo (6)
  • MS Windows (3)
  • could not reproduce (2)
  • 3rd party bug (1)
  • help wanted (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

x11docker is a container tool that runs GUI applications and desktop environments inside Docker and Podman containers with a focus on security.

The core problem x11docker solves is enabling graphical user interfaces to function within containerized environments while maintaining isolation and security boundaries. Traditional container workflows are designed for headless, server-side applications. x11docker bridges this gap by managing the complex interactions between the host's display server and containerized applications. It handles X11 socket forwarding, Wayland protocol bridging, and audio routing through PulseAudio, along with device access for GPUs, webcams, and printers. The tool abstracts away the low-level details of these connections, allowing developers to run GUI applications in containers without manually configuring display sockets, volume mounts, and device permissions.

Developers should adopt x11docker when they need to containerize desktop applications, run isolated GUI tools in sandboxed environments, or deploy full desktop environments within containers. It suits projects requiring strong security boundaries around graphical workloads, such as running untrusted applications safely or isolating development tools. The tool supports both Docker and Podman, making it compatible with different container runtimes. It also provides multiple display backends including X11, Xpra, VNC, and HTML5 viewers, giving flexibility in how graphical output is accessed and displayed.

The project shows consistent maintenance with regular updates addressing both new features and bug fixes. Development activity demonstrates responsiveness to user-reported issues and compatibility challenges across different container runtimes and display protocols. The codebase reflects ongoing refinement of the security model, with attention paid to how privileges and device access are managed within containers. The project maintains documentation of various use cases and configuration options, indicating engagement with a user base that relies on the tool for production workflows.