Design: model UBI as a first-class concept in the bakery OS schema
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- python
- Domain
- build-system
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.
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.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 24
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from posit-dev/images-shared
-
cvp:0 docker tdp:1
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
posit-dev/images-shared#757 · 2 comments ·
Maintainers usually reply within 1 day
-
bug cvp:0 docker priority/medium python tdp:1
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
posit-dev/images-shared#685 ·
Maintainers usually reply within 1 day
-
slack-build-notify: no persisted alert state — causes suppressed repeat-failure and recovery alertsOpenbug cicd cvp:0 docker needs discussion observability tdp:2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
posit-dev/images-shared#677 ·
Maintainers usually reply within 1 day
-
cvp:0 docker tdp:2 tech debt
Difficulty 4/5 3-5 days Newbie friendliness 48/100
posit-dev/images-shared#795 ·
Maintainers usually reply within 1 day
-
cicd cvp:0 docker enhancement tdp:2
Difficulty 5/5 Over a week Newbie friendliness 35/100
posit-dev/images-shared#773 ·
Maintainers usually reply within 1 day
All issues in posit-dev/images-shared
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PedestrianDynamics/pyFDS-Evac#199 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
521xueweihan/HelloGitHub#3790 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sandialabs/atlas-ui-3#978 ·
Maintainers usually reply within 1 day
-
area: tests perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Nitjsefnie-Harness-Commons/daedalus#1255 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4256 ·
Maintainers usually reply within 1 day