posit-dev / posit-dev/images-workbench

Add RHEL 10 (UBI) support for workbench (Standard/Minimal)

Open
#175 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

cvp:3 docker tdp:1
Dominant language
Jinja
Stars
3
Forks
0
Avg merge
1d 5h
Merged PRs (30d)
13

Description

Phase 2 of the RHEL 10 (UBI) initiative (posit-dev/images-shared#575).

Workbench has no RHEL/UBI support today — this is first-time enablement.
posit-dev/images-package-manager#130 (RHEL 10 UBI support) is the
closest precedent.

Approach

  • Standard and Minimal builds on registry.access.redhat.com/ubi10/ubi,
    amd64 + arm64
  • Validate R and Python install and run correctly on RHEL 10 (requires R
    4.6.1+ to avoid the flexiblas-devel issue fixed in
    rstudio/r-builds#329)

Notes

posit_product/main.py's distro-tag resolver already handles Workbench
generically ("rhel" + version) — no code change needed there.

Don't conflate with workbench-session-init's existing rhel8/rhel9/
rhel10 goss checks — those validate bundled remote-session-launcher
binaries for compute targets, unrelated to this image's own base OS.

Out of scope: workbench-session/workbench-session-init (tracked
separately).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review posit_product/main.py to confirm the existing generic RHEL distro-tag handling, then use posit-dev/images-package-manager#130 as the closest implementation precedent. Define Standard and Minimal UBI 10 builds for amd64 and arm64, and validate that R and Python install and run correctly with R 4.6.1 or newer; leave workbench-session and workbench-session-init out of scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, r
Domain
build-system, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.