posit-dev / posit-dev/images-shared

Design: model UBI as a first-class concept in the bakery OS schema

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

Nobody has claimed this yet.

cvp:0 docker tdp:2
Dominant language
Python
Stars
2
Forks
0
Avg merge
4d 13h
Merged PRs (30d)
22

Description

Follow-up from posit-dev/images-shared#575 (RHEL 10 (UBI) image
support).

The bakery OS schema (OSFamilyEnum, SUPPORTED_OS in
posit_bakery/config/image/build_os.py) already models RHEL versions
8/9/10 and sibling distros (Alma, Rocky). It has no concept of "UBI"
anywhere — posit-dev/images-package-manager#130 works around this by
hardcoding registry.access.redhat.com/ubi10/ubi directly in the
Containerfile template rather than expressing it in bakery.yaml.

Question

Is RHEL-family + version sufficient, with "which base image the
Containerfile pulls from" left as an implementation detail (the current
pattern) — or should UBI be a first-class schema concept (e.g. a
baseImage field) before three product repos independently hardcode it?

Notes

Not blocking Phase 1-3 work — package-manager, connect, and workbench
can all follow the existing hardcoded pattern in the meantime.

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

Start with posit_bakery/config/image/build_os.py, especially OSFamilyEnum and SUPPORTED_OS, then inspect the hardcoded UBI reference in posit-dev/images-package-manager#130. Compare the existing RHEL-family schema with the Containerfile pattern. Done means resolving whether UBI belongs in bakery.yaml as a first-class concept or should remain an implementation detail, with the decision documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.