Oracle 9 Desktop

Oracle 9 Desktop is a Kasm Workspaces container image running an Oracle Linux 9 desktop environment, letting you launch and connect to a hosted or remote…

  • Development
  • Network Services
  • Tools & Utilities
Oracle 9 Desktop is a Kasm Workspaces container image running an Oracle Linux 9 desktop environment, letting you launch and connect to a hosted or remote Linux desktop.

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.

66/100 Good

Maintained
100last commit 19 days ago
Popular
47220 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
601.5 GB minimum RAM, runs on ARM
GitHub stars
220
Open issues
0
Last commit
2026-11-02
Activity
declining

Checked yesterday - source: GitHub (oracle/container-images)

Resources & Compatibility

Minimum requirements: 1.5 GB RAM, 10 GB disk. ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Set the app target before installing Before running the exported application SQL, set the workspace, application ID (the app's unique number), schema, and alias. If you skip this, the app can land in the wrong workspace or database schema and cause ID or alias clashes. source
  • Run install scripts in the right order For a split export, run the set_environment script first, then the page or component scripts, and the final end_environment script last. Getting the order wrong can leave pages or settings uninstalled. source
  • Choose tablespace and image path When running the APEX install script, provide the tablespace (database storage area) and image directory you want, such as SYSAUX SYSAUX TEMP /i/. This controls where APEX stores data and images, so a bad path can break the install. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where is the Docker image listed for installation?

The directory entry says it is installable on Docker Hub.

Can the underlying Oracle Linux images be used directly as a final image layer?

No, the Oracle Linux images are intended for use in the FROM field of a downstream Dockerfile.

Can Git history be used to determine what changed between image tags?

No, only the latest tarball for each tag is stored, so changes are documented in a CHANGELOG.

Is Oracle Linux suggested for everyday personal desktop use?

A community reply says it is not the right tool for everyday desktop use compared with Ubuntu, Mint, or Manjaro.

Is Oracle recommended for self-hosting in the community?

A self-hosted community comment says Oracle should not be recommended for self-hosting.

Answers sourced from github.com, ourlocalhost.com, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads