Core Rocky Linux 9

Core Rocky Linux 9 is a KasmVNC container image that provides a clean, isolated Rocky Linux 9 virtual desktop in the browser for running Linux applications…

  • Development
  • Network Services
  • Tools & Utilities
Core Rocky Linux 9 is a KasmVNC container image that provides a clean, isolated Rocky Linux 9 virtual desktop in the browser for running Linux applications without affecting the host.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

36/100 Low

Maintained
50last commit 227 days ago
Popular
61 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
602 GB minimum RAM, runs on ARM
GitHub stars
1
Open issues
0
Last commit
2026-04-08
License
MIT
Activity
stale

Checked 2 days ago - source: GitHub (quenbyako/core)

Resources & Compatibility

Minimum requirements: 2 GB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Check /startupz to see it is ready After starting, open /startupz to confirm it is ready before sending work to it; a 200 response means ready, while a 503 response means it is not ready yet, so wait and check the logs. source
  • Confirm /startupz returns 200 After startup, open /startupz to confirm readiness; a 200 response means ready, while a 503 response means not ready yet, so wait and check the logs. source

Fetched 3 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How is package management handled in the working Rocky Linux 9 FreeBSD jail?

The solved forum thread discusses using microdnf for package management.

Which workloads does a Rocky 9 user discuss for production?

They mention MariaDB and Postfix on medium-scale production servers.

What virtualization layout is discussed for a personal Kubernetes cluster?

A user plans a Proxmox control plane and worker node, possibly adding an ARM SBC as another worker, after earlier success with single-node Fedora CoreOS.

Where do current Rocky Linux issues and fixes get collected?

The Rocky Linux forum has a Common Issues and Questions section for current releases, including fixes or workarounds when applicable.

Answers sourced from forums.freebsd.org, forums.rockylinux.org, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads